[Top] [All Lists]

Re: [2.4 PATCH] bugfix: ARP respond on all devices

To: Carlos Velasco <carlosev@xxxxxxxxxxxx>
Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices
From: David T Hollis <dhollis@xxxxxxxxxxxxxx>
Date: Sun, 17 Aug 2003 12:51:01 -0400
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Lamont Granquist <lamont@xxxxxxxxxxxxxxxx>, Bill Davidsen <davidsen@xxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, bloemsaa@xxxxxxxxx, Marcelo Tosatti <marcelo@xxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, layes@xxxxxxxxx, torvalds@xxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <200308171759540391.00AA8CAB@>
References: <> <> <200308171509570955.003E4FEC@> <200308171516090038.0043F977@> <> <200308171555280781.0067FB36@> <> <200308171759540391.00AA8CAB@>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630
Carlos Velasco wrote:

On 17/08/2003 at 16:28 Alan Cox wrote:

Linux doesn't issue "bad" requests. Linux will reply when it is
asked for an address that it owns, as per RFC826, unless you chose
to change the behaviour with things like arpfilter.

We are not talking about ARP Replies, we are talking about ARP Requests. You can see the Richard post here, same issue I reported several weeks ago:

        On eth0, we see:

11:23:55.650514 0:4:75:ca:c4:ef Broadcast arp 42: arp who-has

Linux is sending an ARP Request to a LAN where the source IP address of
the packet has not any sense in that IP network.
And, at least, 2 RFCs are stating that other devices should not reply
to this packet. Currently know Cisco, Foundry; possibly others, and
possibly others coming as ARP storms are not desired.

Carlos Velasco

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

Check out: I understand the problem you're talking about. It's not a 'bug', it's a feature! You need to use the hidden interface approach to have the back end system not broadcast it's MAC for the virtual IP.

<Prev in Thread] Current Thread [Next in Thread>