All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Double gateway - Two interfaces to same subnet
Date: Mon, 03 Feb 2003 17:43:26 +0000	[thread overview]
Message-ID: <marc-lartc-104429427119088@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104429104413386@msgid-missing>


Oliver,

The reason that arp_filter is not working for you is as follows (let's
tell a little story about an inbound ARP requset):

  - inbound ARP request received on ethernet interface(s)
  - kernel realizes it's for a locally hosted IP
  - it looks up the requestor's IP in its routing table
  - it responds with the link layer address of the interface
    through which it would route IP packets to this requestor

I probably mislead you last week by suggesting that arp_filter was a good
solution for your particular need.  Although it is one of the solutions
for ARP flux, it won't work for your case because of the route lookup
incurred by arp_filter.

Sorry for the lack of clarity on this point in my previous post, Oliver.

As for your ip arp compilation problem....did you patch your kernel, as
well?

  http://www.linuxvirtualserver.org/~julian/arprules-2.4.18-2.diff

The ip arp userspace utility has to have something in the kernel to talk
to!!  :)

 : ... and am I on the right way to solve my initial problem 'two
 : interfaces on the same subnet?'

Absolutely.

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

      reply	other threads:[~2003-02-03 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 16:50 [LARTC] Double gateway - Two interfaces to same subnet Oliver Geisler
2003-02-03 17:43 ` Martin A. Brown [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=marc-lartc-104429427119088@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.