I'm having an insanly difficult time with port forwarding, and I'm not sure why
-
I'm doing some basic port forwarding for bit torrent, VNC, and a Webui based program.
I also have two additional rules to make pfSense pingable, and to allow remote pfsense Webui access.
Attached are images of my port forwards, and firewall rules.
Everything looks fine to me, but alas, n_nothing_ I've set up works.
-
http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting
You shouldn't use vnc the way your doing it.
http://forum.pfsense.org/index.php/topic,6462.0.html
-
http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting
You shouldn't use vnc the way your doing it.
http://forum.pfsense.org/index.php/topic,6462.0.htmlOk, well I really thank you for the VNC update, I've only used it about 5 times max really, so I don't think I've been hacked thus far, but I'll look into hardening the connection.
Anyhow; that still leaves the issue of the other services, etc.
I can assure you that all the basic criteria is met local firewall doesn't exist, ISP is not blocking those ports, client machine is listing on those ports, and it is using pfSense as the gateway.
So I ask, why wouldn't putting in the NAT portforwards, on the WAN interface, to the local IP with the right port number, along with the check box to automatically create the rule, not work?
I haven't used something as advanced as pfSense before, but I know the basics of portforwarding; which is why this is baffling me.
-
How are you testing out these port forwards? Are you using an external connection or are you trying from inside the LAN? If the latter you need to enable nat relfection by making sure the check box is unchecked for "Disable NAT Reflection" on the System -> Advanced menu.
-
VNC should only need TCP, not TCP/UDP. Probably the web ui and the remote too. Don't use TCP/UDP when you only need TCP.
-
alright; I unchecked the NAT reflection box, and that did the trick.
ugh, that was driving me nuts, so I thank you guys a lot.
