mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Allen Lau" <pflau@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] strict interface arp patch for Linux 2.4.2
Date: Thu, 20 Sep 2001 19:34:21 -0400	[thread overview]
Message-ID: <OFEC0F6C6D.00C73EFF-ON85256ACD.00818C46@raleigh.ibm.com> (raw)


Julian Anastasov <ja@ssi.bg> on 09/20/2001 06:19:04 PM

To:   Allen Lau/Raleigh/IBM@IBMUS
cc:   linux-kernel <linux-kernel@vger.kernel.org>
Subject:  Re: [PATCH] strict interface arp patch for Linux 2.4.2




     Hello,

On Thu, 20 Sep 2001, Allen Lau wrote:

>> I want to bring your attention to a Linux ARP patch we plan to use for
load balancing and server
>> clustering.  The available arp filter and hidden patch are not
completely satisfactory. The following

>    Can you explain what setup can't be build using arp_filter,
> hidden or rp_filter and particulary where "hidden" fails for clusters,
> it is very interesting?

The function provided by "hidden" is a necessary element but not
sufficient. I suppose arp_filter
has to be combined with the hidden patch. I dislike hiding an interface,
and the hidden patch is no
longer included in the major distributions which makes delivering a
solution difficult.

In this example, 1.1.1.11 2.2.2.22 are virtual ip's which can float between
boxes and interfaces.
I want virtual ip 1.1.1.11 to be known to clients through eth0 node1
(2.2.2.22 eth1 node2). Node1
can redirect 1.1.1.11 traffic to eth0 node2.
                          node1                                 node2
                      lo:1 1.1.1.11                          lo:1 1.1.1.11
                      lo:2 2.2.2.22                          lo:2 2.2.2.22

              eth0   1.1.1.1     eth1 2.2.2.1         eth0  1.1.1.2   eth1
2.2.2.2
              eth0:1 1.1.1.11
eth1:1 2.2.2.22

On node1, does hiding loopback hide 1.1.1.11? and can 2.2.2.1 be advertised
as source ip in arp
requests from eth0?

>> To generalize, each real server may have multiple nic's of different
types. The task becomes one of
?> maintaining strict identity of each of the real and virtual ip
addresses.  The Linux ARP has the
>> following behaviors which are problematic for maintaining strict
interface identify.
>>
>>    1) box responds to arp on all interfaces on the same wire for an IP
address (arp race)

>    rp_filter and arp_filter can help here but this "arp race" is not
> an evil in some setups

I believe "arp race" may cause purges in a switched network. It certainly
is counter to maintaining
strict interface identity.

Regards
Allen Lau
--
Julian Anastasov <ja@ssi.bg>






             reply	other threads:[~2001-09-20 23:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20 23:34 Allen Lau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-24 21:54 Allen Lau
     [not found] <OFF8C7D800.364E6389-ON85256AD0.00046061@raleigh.ibm.com >
2001-09-23 14:23 ` Julian Anastasov
2001-09-23  2:14 Allen Lau
2001-09-20 16:12 Allen Lau
2001-09-20 18:18 ` David S. Miller
2001-09-20 22:19 ` Julian Anastasov

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=OFEC0F6C6D.00C73EFF-ON85256ACD.00818C46@raleigh.ibm.com \
    --to=pflau@us.ibm.com \
    --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

all inboxes | Powered by JetHome®