Red Hat Bugzilla – Bug 22891
ifconfig not bringing down interface
Last modified: 2007-04-18 12:30:23 EDT
When trying to bring up my 2nd interface up I noticed a strange problem.
Let me try to explain exactly what I was doing. My real IPs have been
Currently we have eth0 up and connected to a
network, /etc/sysconfig/network-scripts/ifcfg-eth0 reads:
and /etc/sysconfig/network reads:
Currently, there is an external machine 18.104.22.168 which I can ping and have
Now I created /etc/sysconfig/network-scripts/ifcfg-eth1 to read:
This interface has no cable connected to it. I then brought up the
interface with ifup eth1, and it failed on adding the route with network
unreachable. Now 22.214.171.124 goes to the local machine and is no longer the
Next, I did ifdown eth1, verified that ifconfig did not show eth1 as being
up, then tried to ping 126.96.36.199. It was then still going to the local
machine (I verified it was local machine from the services running and
ping times), instead of the external 188.8.131.52 as it did before.
In order to get access back to the external 184.108.40.206 machine, I changed
eth1's IP to be 220.127.116.11, brought it up, then back down, and everything was
This does not seem normal to me, am I doing something wrong when bringing
the interface down? ifconfig -a did not show it as being UP when I could
still access 18.104.22.168 as the local machine.
Any help appreciated.
It is normal. IPADDR specifies _your_ IP address on that interface.
But is it normal to keep the IP even when the interface is down? Is there any
other way to truly bring down that interface?