Pleass HELP me! I tryed everything!!
-
Hi guys! Could you help me a bit I am strugling with port fowarding for two days now and I cant configer it properly. I have searched the forum but didn't find anything usefull.
I have tryed everything on this link https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting
When I was testing with packet capture - i could see tha path from wan to lan to server only when using some sort of online port tester (http://ping.eu/port-chk/)
- when i access the ip from 3G I didn't get a response.My network looks something like that:
Modem -> PfSense -> Tp-link router(only doing wifi stuff) -> switch -> hosts
My nat configuration:
source: left default (any)
destination: wan address
port: 6666
redirect ip: 192.168.x.x
port: 8888I didn't add any rule to the firewall because it was added automaticly.
Pleas help me I'm really hopeless.(used to do portforwarding on tplink easily…)
-
Port forwarding on pfsense is no different than on your typical soho, if anything I would argue that its actually easier!!!
You literally have to do like 3 clicks.. port, ip and port.. How is that any different than any other soho router???
You said you tried everying on that troubleshooting doc.. If you did then you would know what you did wrong or what is not working.
You say your port shows up when you check with an online port checker. But doesn't work when you use your 3G device.. What exactly are you trying to access 6666 and 8888 are not standard ports for any sort of application that I am aware of.
Only doing wifi stuff, so you have it in AP mode, how exactly do you have it setup?
In the troubleshooting doc it tells you to sniff. So you see the packets hit your pfsense when when you use your 3g device? If so then sniff on interface your sending it on to the host, this 192.168.x.x IP? Which why are you trying to hide rfc1918 space?
-
for the outside port I have choosen 6666 randomly and 8888 is used for sonarr(to access web GUI).
Thats the problem when I try over 3G I don't see any traffic.
My conf for router:
no dchp server, only wirelless. (what else do you need?)
-
Well so you sniff on your pfsense wan when you try to hit 6666 on your public IP from your phone on 3g.. And you see no traffic.. Well how is that have anything to do with pfsense?? Pfsense can not forward what it does not get..
Maybe your phone company blocks this port, maybe they have you going through a proxy that block it.
So simple test if you sniff on your pfsense wan, and try and access it you will see the traffic - if not then you problem is elsewhere and there is NOTHING you can do on pfsense to fix that something.. Pfsense can not do anything with traffic that doesn't get to it.
-
ok. I tryed now with an vpn connection. And I can see that something is happening on wan connection but nothing is happening on lan.
-
My network looks something like that:
Modem -> PfSense -> Tp-link router(only doing wifi stuff) -> switch -> hosts
Please clarify how the TPlink is connected to pfSense, and how the TPlink is connected to the switch.
Your diagram indicates router-behind-router, but your wording indicates otherwise. If pfSense is connected to the TPlink's WAN port, and the switch is connected to the TPlink's LAN port, then you have a 2nd firewall to dork around with.
-
^ exactly!!!
So now do the same test you did where you see the traffic on your wan.. Do that same sniff on you lan where pfsense is suppose to be sending the traffic.. Does it send it? Does pfsense even have an arp entry for this IP your suppose to be sending too. If your behind a double nat - then no you will not see this arp entry..
Diagnostics, Arp Table.