From: "David S. Miller" <davem@redhat.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Restrict local IP announcements in ARP requests
Date: Mon, 9 Feb 2004 14:08:53 -0800 [thread overview]
Message-ID: <20040209140853.69ab8bea.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402081149001.6268@u.domain.uli>
On Sun, 8 Feb 2004 11:59:35 +0200 (EET)
Julian Anastasov <ja@ssi.bg> wrote:
> I'm proposing simple flag that controls the src selection
> in our ARP requests. I named it arp_announce - mode used to define
> different restriction levels for announcing the local source address
> from IP packets in ARP requests:
I'm fine with this patch, although it appears incomplete because:
> 2 - always use the best source address for this target
The code handling this case is "#if 0/#endif" commented out in your
patch.
Finish this thing up, and as a birthday present to everyone I'll also
add an IN_DEV_ARP_IGNORE flag for inet devices to so people can control
complete ARP ignoring via a global/per-device sysctl.
Hopefully, combined, this will get all the virtual server maniacs off
of my back :-)
next prev parent reply other threads:[~2004-02-09 22:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 9:59 Restrict local IP announcements in ARP requests Julian Anastasov
2004-02-09 22:08 ` David S. Miller [this message]
2004-02-09 22:20 ` David S. Miller
2004-02-09 23:06 ` Julian Anastasov
2004-02-09 23:10 ` David S. Miller
2004-02-10 0:31 ` Julian Anastasov
2004-02-12 4:22 ` David S. Miller
2004-02-15 10:04 ` Julian Anastasov
2004-02-18 3:07 ` David S. Miller
2004-02-18 8:22 ` Julian Anastasov
2004-02-18 21:03 ` David S. Miller
2004-02-10 1:00 ` Julian Anastasov
2004-02-12 4:16 ` David S. Miller
2004-02-12 23:50 ` Julian Anastasov
2004-02-14 7:24 ` David S. Miller
2004-02-14 12:03 ` Julian Anastasov
2004-02-14 20:37 ` 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=20040209140853.69ab8bea.davem@redhat.com \
--to=davem@redhat.com \
--cc=ja@ssi.bg \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).