IPTables NAT: Strange behaviour: bug?
pedro.pandre at gmail.com
Tue Apr 24 10:40:00 CEST 2007
I'm using IPTables to provide me a Port Restricted Cone NAT.
According to STUN RFC, in a Port Restricted Cone NAT
"all requests from the same internal IP address and port are mapped to
the same IP address and port"
(using all policies set to ACCEPT and the following rule:
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE)
My scenario is the following:
-Client behind NAT: IP = 220.127.116.11
-NAT public addr = 192.168.2.159
This client will talk with two different destination addresses:
-192.168.2.164 (Stun server)
-192.168.2.173 (Other NAT's public addr)
In attachment you can find an capture made at the machine with IPTables,
in which you can see:
-packets 1 and 2: Packet going from the client behind NAT
(18.104.22.168:10000) to Stun Server (192.168.2.164:3478) -> Client's
public address is 192.168.2.159:10000
-packets 21 e 22: Packet going from the client behind NAT
(22.214.171.124:10000) to the other NAT's public addr
(192.168.2.173:20000)-> Client's public address is 192.168.2.159:1029
Why is the client getting different NAT mappings?
Why is the mapping changing from
126.96.36.199:10000 -> 192.168.2.159:10000
188.8.131.52:10000 -> 192.168.2.159:1029
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5252 bytes
Desc: not available
Url : /pipermail/netfilter/attachments/20070424/566bd043/nat_strange_behaviour_-0001.obj
More information about the netfilter