[lkml]   [1999]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectARP (mis)behavior
I'm doing some work with network drivers, and have run across some strange
ARP behavior in testing that seems to stem from the IPv4 stack. ARP replies
seem to ignore any mapping between devices and IP addresses, so that as long
as an IP is assigned to one interface all the interfaces on a given machine
will respond to the ARP request.

As a simple example, if a server has two Ethernet cards connected to the
same network configured as and From a client machine,
say, pinging both server addresses seems to work, but looking at
the ARP cache reveals that often one interface has responded to both ARP
requests. More interesting, if one interface is brought down the other will
continue to respond to ARP requests and any other network traffic for the
downed adapters IP address.

In a situation where multiple adapters are on the same network segment, the
Linux IPv4 stack behaves as if a many-to-many mapping of a pool of IP
addresses onto a pool of network adapters exists.

While this does provide some basic fail-over capabilities, I can't imagine
that this is expected or desired behavior. If this is the intended
behavior, I'd be interested in hearing why ARP was implemented this way. If
not, I may have time to try and change this and submit a patch.

(note: I'm having trouble sending to the list from my Intel account, please
ignore the fact that I'm sending from my account)

Chris Leech
Intel Network Communications Group

FREE Email for ALL! Sign up at

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [W:0.045 / U:4.548 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site