From: Thomas Graf <tgraf@suug.ch>
To: David Miller <davem@davemloft.net>
Cc: dsa@cumulusnetworks.com, netdev@vger.kernel.org
Subject: Re: forwarding of ipv4 link local addresses
Date: Wed, 9 Dec 2015 14:44:16 +0100 [thread overview]
Message-ID: <20151209134416.GB11201@pox.localdomain> (raw)
In-Reply-To: <20151203.143531.282555789343463670.davem@davemloft.net>
On 12/03/15 at 02:35pm, David Miller wrote:
> From: David Ahern <dsa@cumulusnetworks.com>
> Date: Tue, 1 Dec 2015 13:35:58 -0800
>
> > RFC 3927 states that packets from/to IPv4 link-local addresses
> > (169.254/16) should not be forwarded, yet the Linux networking stack
> > happily forwards them. Before sending in a patch I wanted to inquire
> > if this behavior is intentional.
>
> It probably won't break anything if we prohibit this, so sure send
> a patch.
I don't have the full email context so apologies if this is not
relevant. The RFC states that such addresses should not be forwarded
_beyond the local link_. So as long as you are not breaking forwarding
of these addresses on the local host, I'm perfectly fine.
I bring this up specifically because of:
commit d0daebc3d622f95db181601cb0c4a0781f74f758
Author: Thomas Graf <tgraf@suug.ch>
Date: Tue Jun 12 00:44:01 2012 +0000
ipv4: Add interface option to enable routing of 127.0.0.0/8
Routing of 127/8 is tradtionally forbidden, we consider
packets from that address block martian when routing and do
not process corresponding ARP requests.
[...]
This feature is being used by a popular PaaS which leverages the
127/8 address space locally without polluting an entire routeable
address space.
next prev parent reply other threads:[~2015-12-09 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 21:35 forwarding of ipv4 link local addresses David Ahern
2015-12-03 19:35 ` David Miller
2015-12-09 13:44 ` Thomas Graf [this message]
2015-12-09 13:46 ` Thomas Graf
2015-12-09 19:04 ` David Ahern
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=20151209134416.GB11201@pox.localdomain \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.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;
as well as URLs for NNTP newsgroup(s).