From: Ard van Breemen <ard@kwaak.net>
To: Adhiraj <adhiraj@linsyssoft.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: arp replies from two adapters of same type in a machine
Date: Fri, 24 Feb 2006 15:57:08 +0100 [thread overview]
Message-ID: <20060224145708.GD17756@kwaak.net> (raw)
In-Reply-To: <1140623158.6987.59.camel@triumph>
Hi,
On Wed, Feb 22, 2006 at 09:15:58PM +0530, Adhiraj wrote:
> I have two RTL-8139 network adapters in a machine, they have these IP
> addresses:
> eth1: 192.168.20.1
> eth2: 192.168.21.1
>
> When I take tcpdump on these interfaces and ping to 192.168.21.1 from
> 192.168.21.50, I see that both the adapters reply to ARP requst sent by
> 192.168.21.50 machine:
I will rephrase what you have:
You have a machine with the ip addresses 192.168.20.1 and
192.168.21.1 configured in the ip stack.
You have 2 nics in the machine which the following routing:
192.168.20.0/24 dev eth1 with default source ip 192.168.20.1
192.168.21.0/24 dev eth2 with default source ip 192.168.21.1
Both nics are on the same network.
Both eth1 and eth2 get an ARP (l2) for 192.168.21.1 (l3), which
according to rfc's should be replied to no matter the source ip.
> Ideally eth1 should not reply to the ARP request.
It should.
If you don't like this behaviour you should use rp-filter for
arp, or use lvs patches to hide the ip address.
PS: this is has nothing to do with proxy-arp. Proxy-arp means you
answer for addresses you can route to. Not for addresses you
already have.
--
begin LOVE-LETTER-FOR-YOU.txt.vbs
I am a signature virus. Distribute me until the bitter
end
prev parent reply other threads:[~2006-02-24 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 15:45 arp replies from two adapters of same type in a machine Adhiraj
2006-02-23 18:44 ` Steven M Campbell
2006-02-24 14:57 ` Ard van Breemen [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=20060224145708.GD17756@kwaak.net \
--to=ard@kwaak.net \
--cc=adhiraj@linsyssoft.com \
--cc=netfilter@lists.netfilter.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.