public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: NIIBE Yutaka <gniibe@m17n.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ARP handling in case of having multiple interfaces on same segment
Date: Thu, 19 Apr 2001 13:07:29 -0400	[thread overview]
Message-ID: <3ADF1B51.87609B3A@nortelnetworks.com> (raw)
In-Reply-To: <200104190042.JAA23614@mule.m17n.org>

NIIBE Yutaka wrote:
> 
> 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.


Under later 2.2 kernels there is something called arp_filter that can be enabled
to give the exact behaviour you want. Apparently it is not yet in 2.4, but I
think that it should definately be added.

See the "ARP responses broken!" thread for more on this.

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

      reply	other threads:[~2001-04-19 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19  0:42 ARP handling in case of having multiple interfaces on same segment NIIBE Yutaka
2001-04-19 17:07 ` Christopher Friesen [this message]

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=3ADF1B51.87609B3A@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=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