Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

If I have

>ip ro dev eth0

another host can obtain my mac address. But if I flush routing info:

>ip ro flush table main

arp resolution doesn't work. Broadcast packets "Who has" reach eth0 but OS (Linux) doesn't respond despite eth0 has address What connection exists between routing and arp resolution?

share|improve this question

migrated from Mar 23 '10 at 12:20

This question came from our site for professional and enthusiast programmers.

Belongs on – Brian Rasmussen Mar 23 '10 at 12:17

On Linux routes are created automatically for the local network when an interface is brought up.

So if you have assigned the ip address to eth0 a routed should be created that looks like this. dev eth0  proto kernel  scope link  src

If that link route does not exist you will not be able to send or receive packets.

By running the command ip ro flush table main you have removed all routes including the link routes from your main route table on the system. From that Linux box you can test things are seriously broken by simpling pinging another IP address. You will get a Network is unreachable error. With no route table at all Linux will not are or really do anything on the network.

You could use a command like this to remove assigned routes without removing the link routes.

ip ro flush table main scope global

This ability to manipulate the link routes does come in handy when you are trying to do something advanced like creating a psuedo-bridge with proxy arp.

share|improve this answer

The described behaviour matches that of an enabled /proc/sys/net/ipv4/*/arp_ignore. arp_filter and rp_filter could lead to similar behaviour under certain circumstances.

arp_ignore - INTEGER
    Define different modes for sending replies in response to
    received ARP requests that resolve local target IP addresses:
    0 - (default): reply for any local target IP address, configured
    on any interface
    1 - reply only if the target IP address is local address
    configured on the incoming interface
    2 - reply only if the target IP address is local address
    configured on the incoming interface and both with the
    sender's IP address are part from same subnet on this interface
    3 - do not reply for local addresses configured with scope host,
    only resolutions for global and link addresses are replied
    4-7 - reserved
    8 - do not reply for all local addresses

    The max value from conf/{all,interface}/arp_ignore is used
    when ARP request is received on the {interface}
share|improve this answer

Your Answer


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