On 11/06/07 14:24, Pascal Hambourg wrote:
You may confuse with the restriction from some RFCs stating that 127.0.0.0/8 addresses are reserved for internal host use, i.e. the loopback interface. There is no such restriction for other addresses that may be configured on the loopback interface. Also, the Linux IP stack follows the "weak" model by default, so any unicast address (except 127.0.0.0/8) configured on any interface can be used for communications on any other interface. So any non-127.0.0.0/8 address configured on the loopback interface can be used for communications on any other interface.
Ok. I did not know for sure as I have not tried this my self and can't say for sure one way or another.
Nope, NAT has nothing to do with this, and the loopback interface is not involved.
In light of the above, agreed.
The old stateless NAT in the routing code controlled with iproute2 is considered broken and all references to it were removed from kernel 2.6.9. But a new stateless NAT is coming with the next kernel release 2.6.24.
...
For now, an ugly workaround may be to use the NOTRACK target in the 'raw' table on the (supposedly) return packets, to skip the connection tracking and the automagic reverse DNAT. I think this will work for DNS over UDP, maybe not so well for TCP.
Yes, "Ugly!". 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
