From: Rick Jones <rick.jones2@hp.com>
To: netdev@vger.kernel.org, tgraf@suug.ch
Cc: David Miller <davem@davemloft.net>
Subject: Re: [PATCHv2 net-next] ipv4: Add interface option to enable routing of 127.0.0.0/8
Date: Tue, 12 Jun 2012 11:13:12 -0700 [thread overview]
Message-ID: <4FD786B8.3030205@hp.com> (raw)
In-Reply-To: <20120612104401.GH28598@canuck.infradead.org>
On 06/12/2012 03:44 AM, Thomas Graf wrote:
> Routing of 127/8 is tradtionally forbidden, we consider
> packets from that address block martian when routing and do
> not process corresponding ARP requests.
I'd go beyond "traditionally forbidden" and call it something considered
fundamental. That 127.0.0.1 (et al) can only be reached by entities on
the same system is rather deeply ingrained in the collective
consciousness after 30-odd years.
> This is a sane default but renders a huge address space practically
> unuseable.
This change would make 127/8 a de facto RFC 1918 address right? It
would not be publicly routable. Are there actually entities who have
exhausted 10/8, 172.16/12 and 192.168/16?
Are there any other stacks which can do this, or would this be an "RFC
1918" network between (newer)Linux systems only? (Assuming
non-newer-linux-based routers would be happy with it)
I cannot say that I'm all that good about practicing the preaching, but
IPv6 cannot be held-off indefinitely.
rick jones
next prev parent reply other threads:[~2012-06-12 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 10:18 [PATCH net-next] ipv4: Add interface option to enable routing of 127.0.0.0/8 Thomas Graf
2012-06-08 20:23 ` David Miller
2012-06-08 22:22 ` Thomas Graf
2012-06-11 23:57 ` David Miller
2012-06-12 10:44 ` [PATCHv2 " Thomas Graf
2012-06-12 11:14 ` Neil Horman
2012-06-12 11:31 ` Thomas Graf
2012-06-12 12:32 ` Neil Horman
2012-06-12 22:26 ` David Miller
2012-06-12 18:13 ` Rick Jones [this message]
2012-06-12 19:50 ` Thomas Graf
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=4FD786B8.3030205@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.