netdev
[Top] [All Lists]

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

To: "Alan Cox" <alan@xxxxxxxxxxxxxxxxxxx>, "Carlos Velasco" <carlosev@xxxxxxxxxxxx>
Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices
From: "Bas Bloemsaat" <bloemsaa@xxxxxxxxx>
Date: Sun, 17 Aug 2003 17:57:26 +0200
Cc: "Lamont Granquist" <lamont@xxxxxxxxxxxxxxxx>, "Bill Davidsen" <davidsen@xxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, "Marcelo Tosatti" <marcelo@xxxxxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, <linux-net@xxxxxxxxxxxxxxx>, <layes@xxxxxxxxx>, <torvalds@xxxxxxxx>, "Linux Kernel Mailing List" <linux-kernel@xxxxxxxxxxxxxxx>
References: <Pine.LNX.3.96.1030728222606.21100A-100000@gatekeeper.tmr.com> <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>
Sender: netdev-bounce@xxxxxxxxxxx
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




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