From: Mark Butler <butlerm@middle.net>
To: David Daney <ddaney@avtrex.com>
Cc: hadi@cyberus.ca, Janos Farkas <chexum+dev@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pgf@foxharp.boston.ma.us, freek@macfreek.nl
Subject: Re: Broadcast ARP packets on link local addresses (Version2).
Date: Fri, 07 Apr 2006 14:38:42 -0600 [thread overview]
Message-ID: <4436CDD2.7010303@middle.net> (raw)
In-Reply-To: <443690C9.5090500@avtrex.com>
David Daney wrote:
> Following your logic through, It seems that you are advocating
> broadcasting *all* ARP packets on *all* link local addresses. That
> would mean that on a 192.168.* switched Ethernet network with DHCP
> that twice as many ARP packets would be broadcast.
192.168.* addresses are not considered "link local", they are rather
"private" or "site local" addresses.
> The scope parameter, as far as I can tell, is used to make routing
> decisions. Overloading it to also implement the RFC 3927 ARP
> broadcasting requirement would result in generation of unnecessary
> network traffic in configurations that are probably the majority of
> Linux deployments.
No extra network traffic, but there is some measurable overhead to
looking up the scope in the routing table.
One problem is having this type of scheme behave properly by default,
i.e. in the absence of user specified entries. Having to create an
entry for every interface in the system just to get RFC standard
behavior is silly.
- Mark
next prev parent reply other threads:[~2006-04-07 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 21:22 [PATCH] net: Broadcast ARP packets on link local addresses (Version2) David Daney
2006-04-06 10:24 ` Janos Farkas
2006-04-06 16:17 ` David Daney
2006-04-06 16:53 ` Janos Farkas
2006-04-07 13:30 ` jamal
2006-04-07 16:18 ` David Daney
2006-04-07 20:38 ` Mark Butler [this message]
2006-04-22 17:14 ` [PATCH] net: " Anand Kumria
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=4436CDD2.7010303@middle.net \
--to=butlerm@middle.net \
--cc=chexum+dev@gmail.com \
--cc=ddaney@avtrex.com \
--cc=freek@macfreek.nl \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pgf@foxharp.boston.ma.us \
/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).