> Now when the Linux box a.b.c.1 (with secondary address d.e.f.1) wants to
> talk to the BSD/OS system d.e.f.2 it does
>
> a.b.c.1 arp who-has d.e.f.2
That is presumably what your routing table says, that both are reachable via
the ethernet
> Which d.e.f.2 promptly ignores, presumably because the IP stack in BSD/OS
> throws it away at a low level, or possibly simply because BSD/OS has no
> idea where to send the ARP response.
probably the latter if the routing table for d.e.f.* is wrong
> Is this already fixed in 2.4 or it is something which needs investigation
> and a patch?
It doesnt look like a bug to me
> According to the standards, who is in the wrong? To me it looks like Linux
> is the misbehaved OS in this case.
I would say Linux is right to use a.b.c.* to talk to d.e.f.*
BSD/OS if it doesnt know where a.b.c.* is but has been told they are not local
is also doing the right thing
Fix your routing tables ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
