Red Hat Bugzilla – Bug 53531
Network setup very unflexible
Last modified: 2014-03-16 22:23:23 EDT
When changing the IP address of a interface, it doesnt always apply when
doing a ifdown / ifup. even network restart doesnt do the job.
I had this happen to me several times while playing with some new servers
and RH Roswell beta 2 (+all updates). One eth was configured for the
external net, one for internal (192...). When changing the 2
configurations around, doing a ifup/down combo, didnt change the network
settings of both, instead they both gor the internal address.
Interstingly enough, this seems to occur when the network card is also
bound to the default gw (router) address. network restart didnt fix this
When doing a 'route' or ip route show, i saw that interface was still
bound to the local network.
My suspission is that the new routing setup (iproute2) is not un-binding
the interface from the routing table, thus is not allowing it to be re-
bound to a different network.
This greatly deacreases the flexibility of linux networking (no longer
can we laugh @ win95 users who need to restart after a network change?!)
Ps, after playing some more, i noticed chaning the IP within the same network
range also did not work. When i tried this, the network cable was unplugged.
However the logs didnt show any errors, nor was there any visual output.
Could it be that when arpping fails, it doesnt change the ip?
This should be fixed at least somewhat in initscripts-6.40.1-1, or later.
*** Bug 55802 has been marked as a duplicate of this bug. ***
*** Bug 55843 has been marked as a duplicate of this bug. ***
Could somebody please post a patch or something so we can fix it in the
I'm still seeing ip addresses persist on an interface after running ifdown.
This is happening with recent versions of initscipts, but only when the
BOOTPROTO is dhcp. After ifdown I see:
# ip addr list dev eth0
2: eth0: <BROADCAST> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:da:b4:13:fd brd ff:ff:ff:ff:ff:ff
inet 192.168.24.4/22 brd 192.168.27.255 scope global eth0
I traced ifdown and it appears that ifdown
- kills the running dhcpcd process for the interface
- uses ip link to take the interface down
Neither of these actions seems to remove the ip address from the device. Is
this a bug in initscripts or in dhcpcd?
dhcpcd, I think.