Issues With Port Forwarding
-
I am having trouble with forwarding ports to host a few game servers on Windows based machines through Steam. I have other virtual servers running on VM of Linux and FreeBSD and the ports working just fine. However when I tried to open ports for Windows machines the ports are still closed. I have also added exceptions in the Windows firewall. Not sure if its a pfSense setting or Windows setting, leaning towards a pfSense setting since these servers work with an ASUS router before I switch to pfSense.
I've tried following these links:
https://doc.pfsense.org/index.php/Online_Gaming_with_pfSense
https://doc.pfsense.org/index.php/Static_Port - With the static port I notice when I put in the specific IP for the Windows machine it reverts to 192.168.1.0
https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting - Not sure if this was helpful though since I have other ports workingMy networking skills are soso I'm still trying to learn basics through my Network+ book so I am at stand still as to what to do next.
-
Nobody can see what you've done unless you show your work.
You'll need to be specific about what has to happen with the NAT.
I am moving this to the gaming forum.
-
I created a standard port forwarding with the associated ports and IP as I did when I forwarded for other services I have opened to the world. They work just fine and as expected. However when I created rules for these Steam games and I check the port its closed but as I said the ports for other virtual server are open. Within the game the server isn't listed in the server browser nor can be connected directly. Forwarding the ports on the ASUS router I had before worked just fine but now I'm on pfSense they don't.
-
Then you're doing it wrong.
Still not posting details asked for.
Good luck.
-
So port forwarding working to X, but not to Y.. How does that have anything to do with pfsense.. If port forwarding was not working for X and Y.. Ok maybe something wrong with pfsense.. But when it works for port X, but not for port Y.. That really points to either you did Y wrong, Or machine your sending Y too is not listing or blocking, etc..
As Derelict has stated multiple times now, if we had some details of your troubleshooting process or setup more than happy to help you put 2nd pair of eyes on it to where your issue is. The troubleshooting doc goes over pretty much ever aspect that could be a problem.
Simple packet captures can tell you were the problem is in like 2 minutes.. Is pfsense getting the traffic to forward? Is it actually forwarding it! This easy to verify with simple sniff on your wan and lan (or other interface your forwarding out of )..
-
Just an observation, static ports are for outbound source ports, not what you want, you want to port forward inbound destination ports. (which technically would be outbound source ports on the replies the destination port would be what they sent in on and if you start rewriting that you are going to break the traffic at the firewall their end)