> > host name and IP address. Both network interfaces are on the same subnet.
> > Depending on which answer is received first, the wrong network interface will
> > be used.
>
> "Wrong" - it is for the machine with that IP. So that makes it right.
>
> > I have tried the arp request on NT4 and HP/UX; both are generating one reply on
> > the correct interface (and my interpretation of the ARP RFC is that the Linux
> > behavior is not correct).
>
> Which specific bit of the RFC ?
>
The 1982 RFC does not specifically address multiple interfaces on one machine,
regardless of whether or not those interfaces are on the same subnet.
So, we need to
(A) ask David C. Plummer (the author of the RFC) if he were to
rewrite his RFC in 1999, would replace the term "machine" with
"interface" (or similar change),
and/or (B) infer the answer, see what makes sense, and see what other OS's
are doing.
I tried to find David C. Plummer (DCP@MIT-MC) but couldn't.
I infer one reply per interface from the RFC as follows:
First, from a high level, the arp request is for an specific IP, not
machine.
Each place in the RFC where "table" is used, it refers to a table where
<protocol type, target protocol address> MAPS TO 48.bit Ethernet address
There should be only one IP address key in the table.
And an IP address is *NOT* meant to have 2 48.bit Ethernet address, as
inferred by "probably replacing any existing entry" in the 2nd sentence
of the 2nd paragraph in the "An Example" section.
Multi IP addresses, on the other hand could be mapped to the same 48.bit
Ethernet address.
Sure, all this could be argued ... arp should be able to handle IP addresses
moving from one piece of hardware to another.
We would like the default arp processing to allow use to control traffic into
a box (thru a switch) by specifying which IP address certain processes send to.
When each box sends 2 arp replies, things get messed up (unless we ignore
these replys and make all our arp tables static).
Alan, what problems to you see with the NT4 and HP/UX behavoir (i.e regardless
of what the RFC says)?
-- Ron
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
