On Fri, 31 Mar 2006 15:26:00 -0800, David Daney wrote:
> From: David Daney
>
> Greetings,
>
> When an internet host joins a network where there is no DHCP server,
> it may auto-allocate an IP address by the method described in RFC
> 3927. There are several user space daemons available that implement
> most of the protocol (zcip, busybox, ...). The kernel's APR driver
> should function in the normal manner except that it is required to
> broadcast all ARP packets that it originates in the link local address
> space (169.254.0.0/16). RFC 3927 section 2.5 explains the requirement.
>
> The current ARP code is non-compliant because it does not broadcast
> some ARP packets as required by RFC 3927.
I haven't seem anyone comment on this, but it would be useful to see this
integrated.
If you have a bunch of Linux machines and two machines have the same
address allocated (not so impossible) they won't notice until they start
communicating with each other.
A third machine attempting to communicate with either party won't be able
to do so. With this patch in place, overlapping assignments are noticed
much faster due to the broadcast.
Something else I've noticed while I've been implementing my zeroconf
daemon is that the kernel returns link-scoped primary addresses first to
'ifconfig'. Unfortunately quite a lot of user-space programs parse its
output and interpret the address it presents as the primary for the
specified interface.
Is that a case of user-space breakage that the kernel team would
ordinarily worry about?
Thanks,
Anand
-
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]
