| 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@xxxxxxxxxxxxxxxxxx> <20030728213933.F81299@xxxxxxxxxxxxxxxxxxxxxxxxx> <200308171509570955.003E4FEC@xxxxxxxxxxxxxx> <200308171516090038.0043F977@xxxxxxxxxxxxxx> <1061127715.21885.35.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <200308171555280781.0067FB36@xxxxxxxxxxxxxx> <1061134091.21886.40.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| 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 |
| Previous by Date: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Alan Cox |
|---|---|
| Next by Date: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Carlos Velasco |
| Previous by Thread: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Alan Cox |
| Next by Thread: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Carlos Velasco |
| Indexes: | [Date] [Thread] [Top] [All Lists] |