From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Bas Bloemsaat" Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices Date: Sun, 17 Aug 2003 17:57:26 +0200 Sender: netdev-bounce@oss.sgi.com Message-ID: <011a01c364d8$44be1f90$c801a8c0@llewella> References: <20030728213933.F81299@coredump.scriptkiddie.org> <200308171509570955.003E4FEC@192.168.128.16> <200308171516090038.0043F977@192.168.128.16> <1061127715.21885.35.camel@dhcp23.swansea.linux.org.uk> <200308171555280781.0067FB36@192.168.128.16> <1061134091.21886.40.camel@dhcp23.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: "Lamont Granquist" , "Bill Davidsen" , "David S. Miller" , "Marcelo Tosatti" , , , , , "Linux Kernel Mailing List" Return-path: To: "Alan Cox" , "Carlos Velasco" Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org What wonders me about the behaviour is that it is not consistent. When I have the following situation: a box with twon nics, one 192.168.1.1, ethernet adr aa , the other 192.168.1.2 ethernet adr bb When I do an ARP request for 192.168.1.2, both respond. aa as wel as bb But if I do another request for 192.168.1.2, and I direct it to the aa NIC, it does not respond. Unless I turn on packet_forwarding (i.e. routing). Remember, ARP is not routable, or shouldn't be, yet it is treated as such. Regards, Bas