Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

First of all, here is my /etc/network/interfaces

auto lo 
iface lo inet loopback 

auto eth0 
iface eth0 inet static 

auto eth1 
iface eth1 inet static 

At boot time, both eth1 and eth0 are reachable and usable.

I shut down my eth1 interface with

ifdown eth1

My ifconfig does not show my eth1 interface.

But, when i try to ping (the ip address attached to my eth1), it pings!

I don't think that should be the normal behavior. If so, can you explain me why? Why can we ping an "ifdowned" interface?

share|improve this question
If you ifdown eth1 AND you physically unplug the cable to eth1, can you still ping ? – Steven Monday Jan 21 '11 at 16:06
No, already tested – ohe Jan 21 '11 at 16:19
Can you throw up the output of "route -n" as well? – Niall Donegan Jan 24 '11 at 10:20
up vote 1 down vote accepted

It looks like both interfaces are connected to the same subnet and same broadcast domain. Are you sure there isn't another device on the network that also has the ip of Maybe when you drop eth1, it's then pinging via eth0?

I would try running Wireshark/tshark on the two interfaces (separately) when eth1 is down, and seeing where the packets are going.

share|improve this answer
In fact, and after verification. Both interfaces are connected to the same ... hardware interface. I think that this is the explanation of this behavior. – ohe Jan 24 '11 at 10:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.