[ previous ] [ next ] [ threads ]
 From:  =?iso-8859-1?Q?P=E5l_Borsheim?= <paal at tgmsound dot com>
 To:  "'Molle Bestefich'" <molle dot bestefich at gmail dot com>
 Cc:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  SV: [m0n0wall] Re: Can't NAT on m0n0wall.
 Date:  Wed, 21 Jun 2006 09:34:27 +0200
Thanks for answering.

Hmmmmm. If I understand U here right U mean that the firewall filter is not
suppose to work that way. If I am to enter the rules twice one for
translated address and one for untranslated address then this is not right.

Pleas read answer to Chris Buechler and the list and see if there is
somethig wrong here. :)

Thaks for the answer. :)


-----Opprinnelig melding-----
Fra: Molle Bestefich [mailto:molle dot bestefich at gmail dot com] 
Sendt: 21. juni 2006 07:34
Til: paal at tgmsound dot com
Kopi: m0n0wall at lists dot m0n0 dot ch
Emne: [m0n0wall] Re: Can't NAT on m0n0wall.

Pål Borsheim wrote:
> I have workt with a lot of ruters, gateways and firewalls but this 
> m0n0wall is strange.
> I have tryed now for some time to NAT any port from my external / 
> public IP to a server on my intra network.

In my experience, m0n0wall is broken in a way that causes the firewall
filter engine to see both translated and non-translated addresses.

To make NAT work on m0n0wall, I created twice all rules that pertain to
networks and devices with NATed addresses - one rule using the translated
address and one rule using the untranslated.

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch