-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
lukas@xxxxxxxxxxx wrote:
I have strange problem with NAT.
Me too.
I have kernel 2.6.14.7-5 and iptables-1.3.3-6@xxxxxxxxxx and I use nat
Tested with 2.6.11 and 2.6.16.4.
NAT configuration is simple but some packets are not NATed - on my
public interface packets with source address of my internal (NATed)
network appears and i have no clue what is wrong.
I have very simple rules too. nat/PREROUTING is empty and
nat/POSTROUTING contains only one rule with MASQUARADE target on
interface with public IP (Policies are ACCEPT). I don't use ROUTE target
anywhere.
16:30:39.015880 IP (tos 0x0, ttl 127, id 28594, offset 0, flags [DF],
proto: TCP (6), length: 40) 10.10.10.104.3689 > 83.29.48.50.6881: F,
cksum 0x1623 (correct), 3885889894:3885889894(0) ack 3151418643 win 65535
Exactly. I can see only FIN packets which are not translated. After
looking into conntrack table, I think MASQ ignores FIN packets that are
missing in conntrack table (Is it INVALID or NEW state?).
Very strange behaviour have counters too. These strange packets are not
loggable after MASQ rule. It seems like a bug.
I test it also on kernel 2.4.32-6 and its bad too.
