Usually whenever I get these kinda problems I delete the rule and set it again, which always seems
to work. Make sure you use the "auto add firewall rule" when creating the NAT rule, failure to do
so can cause problems I know from experience.
However, it that doesn't work I'd start looking in the other end first. Does port 2023 work
internally? Is there a firewall in use at the unix server side? Can you access canyouseeme.org from
the unix server and see if it actually does work and there's something else all together?
Från: Frank Bello [mailto:fbello at bytcorp dot com]
Skickat: den 24 april 2013 03:16
Till: m0n0wall at lists dot m0n0 dot ch
Ämne: [m0n0wall] Port Forwarding problem on 2023
I've been testing the M0n0wall appliance in an ESX 3i host and have been very pleased with it.
However I wonder if someone can help me find out how come a port/NAT forwarding rule that I'm trying
to set for port 2023 is not working.
The rule allows access to the outside TELNET clients to an internal UNIX server which is listening
for TELNET connections on port 2023
I have setup forwarding rules for RDP on 3389 and for VMWARE client management on SSL and other
private ports and it works perfectly. However when I tell it to forward 2023 it does not. And only
in that rule.
I have also tried to create another rule where the external port 23 will be forwarded to the
internal 2023, but that does not work neither
Following are the pages from my setup. Any help ? thanks in advance.
Firewall: NAT: Inbound
If Proto Ext. port range NAT IP Int. port range Description WAN TCP 3389 10.10.10.10 3389
RDP Service WAN TCP/UDP 443 (HTTPS) 10.10.10.100 443 (HTTPS) VMWARE SSL WAN TCP/UDP 902 -
903 10.10.10.100 902 - 903 VMWARE WAN TCP/UDP 2023 10.10.10.11 2023 UNIX Server Access
Proto Source Port Destination Port Description
TCP * * 10.10.10.10 3389 NAT RDP Service
TCP/UDP * * 10.10.10.100 902 - 903 NAT VMWARE
TCP/UDP * * 10.10.10.100 443 (HTTPS) NAT VMWARE SSL
TCP/UDP * * 10.10.10.11 2023 NAT