| To: | "Carlos Velasco" <carlosev@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [2.4 PATCH] bugfix: ARP respond on all devices |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sun, 27 Jul 2003 16:58:31 -0700 |
| Cc: | bloemsaa@xxxxxxxxx, marcelo@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, layes@xxxxxxxxx, torvalds@xxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <200307280158250677.10891156@xxxxxxxxxxxxxx> |
| References: | <Pine.LNX.4.53.0307272239570.2743@xxxxxxxxxxxxxxxxxxxx> <200307280140470646.1078EC67@xxxxxxxxxxxxxx> <20030727164649.517b2b88.davem@xxxxxxxxxx> <200307280158250677.10891156@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 28 Jul 2003 01:58:25 +0200 "Carlos Velasco" <carlosev@xxxxxxxxxxxx> wrote: > On 27/07/2003 at 16:46 David S. Miller wrote: > >Bas's problem can be solved by him giving a "preferred source" > >to each of his IPV4 routes and setting the "arpfilter" sysctl > >variable for his devices to "1". > > Yes, it's another approach to solve his problem. But he must play with > routing. Precisely he must, because he has misconfigured routes for the behavior he desires. His problem is about source address selection when trying to contact a given destination. If there is no specific source address specified, the kernel may legally use any source address, and this decision extends to ARP handling as well. It's totally illogical to say that it's easier for him to patch his kernel and reboot it than fix his route configuration. |
| Previous by Date: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Carlos Velasco |
|---|---|
| Next by Date: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Michael Richardson |
| Previous by Thread: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Carlos Velasco |
| Next by Thread: | Re: [2.4 PATCH] bugfix: ARP respond on all devices, Carlos Velasco |
| Indexes: | [Date] [Thread] [Top] [All Lists] |