From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Loopback security...
Date: Fri, 25 Apr 2008 15:00:10 -0500 [thread overview]
Message-ID: <4812384A.2040309@riverviewtech.net> (raw)
In-Reply-To: <480F14C3.3010403@plouf.fr.eu.org>
On 4/23/2008 5:51 AM, Pascal Hambourg wrote:
> Ah, I see what this is all about. The problem is not the loopback
> interface, it is the loopback address range 127.0.0.0/8. Some RFC states
> that "127.0.0.0/8 must not be used outside a host", so the routing code
> in the Linux kernel discards packets with a source or destination
> address in this range which are sent or received through a non loopback
> interface.
Ok. That very clearly explains why I was seeing what I was seeing.
Thank you. It also explains that little (if any thing) will get around
this with the kernel behaving the way that it is.
<snip>
*nod* (to all)
> What behaviour ? Discarding traffic to or from 127.0.0.0./8 on a non
> loopback interface ? I guess there have been some patches.
Interesting.
Grant. . . .
next prev parent reply other threads:[~2008-04-25 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 2:05 Loopback security Grant Taylor
2008-04-22 11:01 ` Leonardo Rodrigues Magalhães
2008-04-22 14:08 ` Grant Taylor
2008-04-22 16:04 ` Pascal Hambourg
2008-04-22 19:43 ` Grant Taylor
2008-04-23 10:51 ` Pascal Hambourg
2008-04-25 20:00 ` Grant Taylor [this message]
2008-04-22 20:51 ` Petr Pisar
2008-04-23 9:31 ` Pascal Hambourg
2008-04-23 9:45 ` Leonardo Rodrigues Magalhães
2008-04-22 16:50 ` Leonardo Rodrigues Magalhães
2008-04-22 20:07 ` Grant Taylor
2008-04-22 20:25 ` Leonardo Rodrigues Magalhães
2008-04-23 0:38 ` Grant Taylor
2008-04-23 9:07 ` Pascal Hambourg
2008-04-23 9:44 ` Pascal Hambourg
2008-04-22 19:48 ` Jan Engelhardt
2008-04-22 20:16 ` Grant Taylor
2008-04-23 15:22 ` Jan Engelhardt
2008-04-25 20:11 ` Grant Taylor
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=4812384A.2040309@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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