From: NIIBE Yutaka <gniibe@m17n.org>
To: linux-kernel@vger.kernel.org
Subject: ARP handling in case of having multiple interfaces on same segment
Date: Thu, 19 Apr 2001 09:42:01 +0900 (JST) [thread overview]
Message-ID: <200104190042.JAA23614@mule.m17n.org> (raw)
Sometime, we have setting like following (say, in the migration
process of changing IP networks, or perhaps wrong way of load
balancing):
+----------+
|eth0 eth1 |
+----------+
| |
-------+---+------------
Current implementation of Linux doesn't handle this case. The problem
is ARP handling. When ARP broadcast packet comes to the host, both
interfaces receive the packet, and regardless of the device, we reply
to that packet. I think that we should not reply if the packet is not
related to that interface. If the ARP request is for eth1's address,
we should not send reply from eth0.
IIRC, I had fixed this issue six years ago, but now see same thing.
Kind a dejagnu...
How do you think? For me, this is bug.
--
next reply other threads:[~2001-04-19 0:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 0:42 NIIBE Yutaka [this message]
2001-04-19 17:07 ` ARP handling in case of having multiple interfaces on same segment Christopher Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200104190042.JAA23614@mule.m17n.org \
--to=gniibe@m17n.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox