All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Steer <gsteer@lidcam.com.au>
To: lartc@vger.kernel.org
Subject: [LARTC] arp control in a multihomes host
Date: Mon, 02 Sep 2002 02:34:30 +0000	[thread overview]
Message-ID: <marc-lartc-103093408322077@msgid-missing> (raw)

I have a problem involing arp table entries that I'm hoping someone can
help with.

I'm working on a mail system that utilises multiple Linux servers in a
redundant configuration.
The configuration has pairs of Linux servers running as MTAs. Each pair
of real servers hides behind a virtual server name. The virtual server
name and load balancing of real servers is handled by an Alteon AD3 switch.
Each of the Linux servers has two ethernet interfaces with the second
interface also connected to a (second) Alteon. The two Alteons are
configured in an active-standby arrangement using VRRP.
The IP addresses of each linux servers' ethernet interfaces are on the
same subnet (172.16.180.0/128),

The configuration of the Alteon causes each of the Alteon IP
addresses to appear on each interface of the Linux box, with the same
MAC address i.e.

alteon1 (172.16.180.2) at 00:00:E8:D7:4F:5D [ether] on eth0
alteon2 (172.16.180.3) at 00:50:BA:CB:DD:D8 [ether] on eth0
alteon1 (172.16.180.2) at 00:00:E8:D7:4F:5D [ether] on eth1
alteon2 (172.16.180.3) at 00:50:BA:CB:DD:D8 [ether] on eth1

What I'm looking to do is to not have the second entry for any host
appear in the arp table if it's already there for another interface.
i.e. if alteon1 has an arp entry pointing to eth0, don't add one for
eth1 - which I guess means, don't issue arp requests/responses on the
other interface for an Alteon if we have an arp table entry.
The solution doesn't need to be tailored to the Alteon IP
addresses, just a general rule of not issuing arp requests/responses
on a second interface if we already have a similiar entry pointing to
the first interface.

Regards
Geoff Steer




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-09-02  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  2:34 Geoff Steer [this message]
2002-09-02  2:50 ` [LARTC] arp control in a multihomes host Martin A. Brown
2002-09-02  7:04 ` M.F. PSIkappa

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=marc-lartc-103093408322077@msgid-missing \
    --to=gsteer@lidcam.com.au \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.