Port forwarding set, port still closed
-
@Octopuss Try to enable NAT Reflection mode for port forwards in pfSense.
-
@Bob-Dig I vaguely remember this mentioned elsewhere. BUT I am absolutely certain I never changed this and I know for a fact both ports were open. The only thing I have changed in the past year is updating from pfSense 2.6.x to 2.7
edit: flipped it to enabled, rebooted just to be safe, and the port for my machine is still closed.
-
@Gertjan said in Port forwarding set, port still closed:
The WAN firewall (NAT) rules ?
You've shown the two NAT rules.
With every NAT rule, there is also a corresponding firewall rule, typically on the WAN interface.
Show that firewall rule... !? -
Also, it's not that anything isn't working, quite the opposite:
But from what I remember, if port a torrent client is running on is not opened to the outside, no direct connections can be made, and the amount of seeders or leechers is limited. Bittorrent has some tech that makes it running regardless, but... you know.
Plus I know it used to work and I didn't change anything, so WTF is going on? And on top of that, it only doesn't "work" for my own PC, not the server. I'm just puzzled. -
@Gertjan I can't post here anymore because something is flagging it as spam.
edit: ok, finally
-
Ok : good :
Both are receiving traffic :
A boat load of states, like the good old torrent uses to have.
-
@Gertjan Yup, but why the heck this...
-
@Octopuss Many (or any) port checkers can only do TCP. But in your log you should see the connection from that site.
-
@Bob-Dig Fair enough, but why is the server's port open when it uses exactly the same bittorrent client with the same configuration? (TCP+UDP).
-
@Octopuss Ha, problem identified: ESET Smart Security's firewall. I have no idea what it does, but it blocks this. I forgot the software had actual firewall in it. Now I have to dig into the settings, bleh.
