I tried to solve problem with simple trick (like disable proxy arp or change
routing info), but I couldn't. Then, I realized that the problem was at
"kernel" level, cause I had:
host interface
HOST1 shaper0 (eth0)
So, when HOST1 started up, kernel (wrongly) sent it an ARP REPLY cause source
interface was different from destination interface (for the host). This is
really wrong, I think, cause shaper0 is the SAME interface (at physical
level, where proxy arp works) of eth0 (it uses same first 2 level ISO/OSI,
shaper has to be managed exactly as eth0).
In the end I say that I prefer kernel mode solution, rather than use mode
solution.
I Hope to has been clear.
Let me know what you think.
Regards
Roberto Arcomano
Il 15:24, marted́ 18 settembre 2001, hai scritto:
> Hello,
>
> On Tue, 18 Sep 2001, Roberto Arcomano wrote:
> > Hello Julian,
> > thank you very much for your answer. I'm sure your solution would be ok,
> > but I think the right solution should be modify the kernel, cause, shaper
> > device cannot be managed like a physical device (I mean about route check
> > before sending ARP REPLY): I think it is more clear than other solutions.
>
> If this is true then you have to provide support for all
> other devices, for example, tunnels. The common for such setups is
> that asymmetric routing is used. OTOH, your change drops the ARP
> probe without updating the neighbour state. BTW, do you see any
> incoming traffic on the shaper device?
>
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
-------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/