Re: NAT rewriting port, breaking the rules

Chris Buechler <[email protected]>
Newsgroups gmane.comp.security.firewalls.m0n0wall
Message-ID <[email protected]>
On Thu, Jan 27, 2011 at 2:51 PM, Michael <[email protected]> wrote:
>
> 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?

Did you reset states after changing that? Otherwise the connections
that were already active will stay that way as long as they're active,
which will be forever with SIP.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.