From: Andi Kleen <ak@suse.de>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: "David S. Miller" <davem@redhat.com>,
Ben Greear <greearb@candelatech.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] arp_filter patch for 2.4.4 kernel.
Date: Sun, 6 May 2001 10:34:50 +0200 [thread overview]
Message-ID: <20010506103450.A29403@gruyere.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0105051550000.20277-100000@twinlark.arctic.org> <Pine.LNX.4.33.0105051556280.20277-100000@twinlark.arctic.org>
In-Reply-To: <Pine.LNX.4.33.0105051556280.20277-100000@twinlark.arctic.org>; from dean-list-linux-kernel@arctic.org on Sat, May 05, 2001 at 03:57:38PM -0700
On Sat, May 05, 2001 at 03:57:38PM -0700, dean gaudet wrote:
> also -- isn't it kind of wrong for arp to respond with addresses from
> other interfaces?
Usually it makes sense, because it increases your chances of successfull
communication. IP addresses are owned by the complete host on Linux, not by
different interfaces.
For some weirder setups (most of them just caused by incorrect routing
tables, but also a few legimitate ones; including incoming load balancing
via multipath routes) it causes problems, so arpfilter was invented to
sync ARP replies with the routing tables as needed.
>
> what if ip_forward is 0? or if there's some other sort of routing policy
> in effect?
ARP filter has nothing to do with forwarding.
There is magic ARP proxying if linux knows the answer to an ARP request
on a different interface, but it's a completely independent thing.
-Andi
next prev parent reply other threads:[~2001-05-06 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 0:08 Ben Greear
2001-05-05 21:35 ` Ben Greear
2001-05-05 22:28 ` David S. Miller
2001-05-05 22:53 ` dean gaudet
2001-05-05 22:57 ` dean gaudet
2001-05-06 8:34 ` Andi Kleen [this message]
2001-05-06 16:35 ` Mark Hahn
2001-05-05 23:27 ` David S. Miller
2001-05-05 23:52 ` David S. Miller
2001-05-06 7:20 ` Ben Greear
2001-05-06 8:40 ` Andi Kleen
2001-05-13 22:39 ` Harald Welte
2001-05-07 16:35 ` Matthew Kirkwood
2001-05-13 6:37 ` Ben Greear
2001-05-13 7:45 ` David S. Miller
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=20010506103450.A29403@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®