Janos Farkas wrote:
On 2006-04-05 at 14:22:08, David Daney wrote:
The changes in this version are that it tests the source IP address
instead of the destination. The test now matches the test described
in the RFC. Also a small cleanup as suggested by Herbert Xu.
Some comments on the first version of the patch suggested that I do
'X' instead. Where 'X' was behavior different than that REQUIRED by
the RFC (the RFC's always seem to capitalize the word 'required').
The reason that I implemented the behavior required by the RFC is so
that a device running the kernel can pass compliance tests that
mandate RFC compliance.
Sorry for chiming in this late in the discussion, but... Shouldn't it
be more correct to not depend on the ip address of the used network,
but to use the "scope" parameter of the given address?
RFC 3927 specifies the Ethernet arp broadcast behavior for only
169.254.0.0/16. Presumably you could set the scope parameter to local
for addresses outside of that range or even for protocols other than
Ethernet. Since broadcasting ARP packets usually adversely effects
usable network bandwidth, we should probably only do it where it is
absolutely required. The overhead of testing the value required by the
RFC is quite low (3 machine instructions on i686 is the size of the
entire patch), so using some proxy like the scope parameter would not
even be a performance win.
David Daney
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
