Hello All,

Disregard my previous email that the issue was resolved, because it wasn't. By doing what I stated,
it overwrites the WAN IP rules on the default interface. I'm going to review what the other
gentleman wrote...

Thanks,
-Ben


-----Original Message-----
From: Ben R. Serebin [mailto:ben " a t" reefsolutions " d o t " com]
Sent: Fri 12/9/2005 5:48 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] Issues with Server NAT & 1:1 for port fwding
 
Hello All,

Wow... great UI.... note sarcasm. (If you want me to contribute info to docs, let me know.) Found
the problem with Server NAT. One must not select the External Address for the 2nd WAN IP on Inbound
NAT rules. Leave it at "Interface address" for Server NAT under Firewall:NAT rule.

Example of how to add protocol after adding IP in Server NAT.

Interface: WAN
External address: (leave it on Interface address)
Protocol: select protocol (e.g. SMTP)
External port range: (e.g. SMTP)
NAT IP: (e.g. internal IP of server hosting protocol)
Local port: (e.g. SMTP)
Description: (e.g. SMTP on Server 2)
[check this box] Auto-add a firewall rule to permit traffic through this NAT rule
[select Apply changes]

-Ben