Re: Loopback security...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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. . . .
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux