[ previous ] [ next ] [ threads ]
 
 From:  Michael <monowall at encambio dot com>
 To:  M0n0wall List <m0n0wall at lists dot m0n0 dot ch>
 Subject:  NAT rewriting port, breaking the rules
 Date:  Thu, 27 Jan 2011 20:51:41 +0100
Hello list,

Has anyone else seen this behaviour? To provide a SIP proxy with
the help in needs in overcoming NAT for telephony applications,
m0n0wall can be configured to 'Disable port mapping' in the tab
Firewall/NAT/Outbound entries.

When I check 'Disable port mapping', almost all packets leaving
the NAT have the same port number as that which the sending devices
used.

The problem is that m0n0wall's NAT logic does indeed rewrite the
port number on some packets. This causes problems at the receiving
end.

Why is m0n0wall rewriting the port number of packets when 'Disable
port mapping' is enabled? Is it because of something in the Traffic
shaper maybe?

Regards,
Michael