From: Daniel Gryniewicz <dang@fprintf.net>
To: Julian Anastasov <ja@ssi.bg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG?] unwanted proxy arp in 2.4.19-pre10
Date: 16 Jul 2002 16:04:50 -0400 [thread overview]
Message-ID: <1026849894.3520.5.camel@athena.fprintf.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0207162148040.1484-100000@u.domain.uli>
On Tue, 2002-07-16 at 18:32, Julian Anastasov wrote:
>
> Hello,
>
> It seems you don't like the way ARP is replied in Linux. But
> note that ARP follows IP, i.e. Linux replies on each device where it
> is willing to accept IP for the same path. Such behaviour is caused by
> the way IP is set by default in RFC1812: Source Address Validation
> is disabled (rp_filter=0).
>
<heavily snipped>
Okay, I have no problem with this. What I have a problem with is Linux
sending an ARP request out an interface and using the address of
*another interface* as the tell address. This is just broken.
--
Recursion n.:
See Recursion.
-- Random Shack Data Processing Dictionary
next prev parent reply other threads:[~2002-07-16 20:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 22:32 Julian Anastasov
2002-07-16 20:04 ` Daniel Gryniewicz [this message]
2002-07-16 23:41 ` Julian Anastasov
-- strict thread matches above, loose matches on Subject: below --
2002-07-14 22:35 Julian Anastasov
2002-07-15 5:40 ` David S. Miller
[not found] <20020713.205930.101495830.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0207141026440.4252-100000@twinlark.arctic.org.suse.lists.linux.kernel>
2002-07-14 18:40 ` Andi Kleen
2002-07-15 5:37 ` David S. Miller
2002-07-14 10:34 Julian Anastasov
2002-07-23 22:06 ` Bill Davidsen
2002-07-13 16:21 Bill Davidsen
2002-07-13 18:28 ` Alan Cox
2002-07-13 19:19 ` Gerhard Mack
2002-07-14 1:52 ` Alan Cox
2002-07-14 3:17 ` Bill Davidsen
2002-07-14 3:59 ` David S. Miller
2002-07-14 17:29 ` dean gaudet
2002-07-15 1:39 ` Bill Davidsen
2002-07-15 5:45 ` David S. Miller
2002-07-15 10:39 ` Bill Davidsen
2002-07-15 1:46 ` Bill Davidsen
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=1026849894.3520.5.camel@athena.fprintf.net \
--to=dang@fprintf.net \
--cc=ja@ssi.bg \
--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®