From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: netdev@vger.kernel.org
Subject: Re: Link-local address handling for IPv4
Date: Tue, 22 Jun 2010 19:21:35 +0200 [thread overview]
Message-ID: <1277227295.3057.697.camel@edumazet-laptop> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E739702DDAE@GVW1118EXC.americas.hpqcorp.net>
Le mardi 22 juin 2010 à 13:17 +0000, Fischer, Anna a écrit :
> Hi,
>
> Does the Linux kernel network stack do any specific handling of
> link-local address configuration and handling according to RFC 3927?
> I know that there is user-level code like Zeroconf / Avahi and these
> tools create ARP sockets directly on the specified network interfaces
> in order to support link-local address handling. But if I do not
> run any of these tools, does the kernel's ARP code take care of this, too?
>
There is no RFC 3927 support in kernel, you need user space support (or
switch to DHCP ;) )
Note that ARP replies MUST also be broadcasted for this particular
169.254/16 network (RFC 3927, 2.5), you need a kernel patch too, this
was discussed 4 years ago on netdev, and nothing was decided/changed.
http://marc.info/?l=linux-netdev&m=114427223811197&w=2
BTW I believe that our forwarding path doesnt test source/destination
address not being part of 169.254/16 network, I am not sure it
is a real problem or not. A netfilter rule can fix it eventually.
7. Router Considerations
A router MUST NOT forward a packet with an IPv4 Link-Local source or
destination address, irrespective of the router's default route
configuration or routes obtained from dynamic routing protocols.
A router which receives a packet with an IPv4 Link-Local source or
destination address MUST NOT forward the packet. This prevents
forwarding of packets back onto the network segment from which they
originated, or to any other segment.
prev parent reply other threads:[~2010-06-22 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 13:17 Link-local address handling for IPv4 Fischer, Anna
2010-06-22 17:21 ` Eric Dumazet [this message]
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=1277227295.3057.697.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=anna.fischer@hp.com \
--cc=netdev@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