[Solved] I'm apparently unable to port forward...
-
Hi.
I tried everything I could to make port forwarding work, but it doesn't.
I don't really think it's my ISP since port forwarding works nicely on my Mikrotik router.
I don't have any blocking rule above the port forwarding rules. they're on top of everything.
here's my config:
######################
######################
Thank you!
-
Dude it is ALWAYS PEBKAC.. I can understand frustration when something doesn't work.. But in the 10+ years I have been here it is always something the user overlooks or doesn't do, etc.
Did you go through the troubleshooting guide - it will allow you find where the problem is in a few minutes.
For starters you have NO rule on your WAN... How is 8889 going to get to your 192.168 address when you do not have a rule listed on your wan to allow it. When you create the port forward it will automatically create this rule for you unless you tell it not too.. So where is the rule? It would look like this.
As to not pinging your WAN address.. Simple sniff on your wan when you do that - does it GET there??? That takes all of 30 seconds to do.. Your rule has zero hits on it.. So you can not allow for ping if pfsense never sees the request..
-
I tried manually adding a rule allowing port 8889 at WAN Address, but also didn't work.
-
And SNIFF does it GET there??? Seems your pings are not.. So who says 8889 is? What do you have front of pfsense?
Simple diag, packet capture wan... port 8889 then do your test.
Mines not going to work since I don't have anything at 192.168.10.6 - but you can see the traffic got to my wan
-
nothing... just a media converter (fiber>ethernet) and it's "bridged" by default..
that website can't ping me, but that one friend on another city can, but he can't access my website..
-
I also tried using things like "free proxy" to access the website (hosted on 8889) but didn't worked.
-
First step into troubleshooting is SNIFF!!! IF the traffic doesn't get to pfsense wan it is IMPOSSIBLE for it to be forwarded..
PM me your wan IP and I will attempt ping
-
what do you mean by sniff?
-
Packet capture under diagnostics - I posted example above of hitting 8889 to my IP.
-
here
Start the capture - then use like can you see me to that port... Do you see the traffic??
-
-
So if NOTHING gets to your wan - how could pfsense ever forward it??
Pfsense can not forward what it doesn't see - pfsense has ZERO control of traffic getting to its wan.. You need to look upstream
-
I don't know, dude.. I don't know what's happening
-
Get with your ISP on why your not seeing that traffic.. Pfsense can NOT forward what it doesn't see!! Its that simple..
-
@ninom4ster said in I'm apparently unable to port forward...:
that website can't ping me, but that one friend on another city can, but he can't access my website..
PM me your IP... I will setup a ping to your IP... Lets see if you answer. If does or doesn't even you can sniff while doing it.
-
I already called them. they're not blocking anything. and as I said, it works perfectly with my Mikrotik. (with the exact same ports open)
-
Well they are lying or don't understand what your asking... If you sniff and there is nothing there for that port - then pfsense can never forward traffic that doesn't get to it!!
I have ping going - and NOTING.
PM you my IP.. Sniff for it..
-
Get a ping going to my IP... And will validate your coming from that IP..
keep it running with -t if windows...
-
I also "sniffed" the port 80, because that's where the web page is hosted on, locally..
internet > TCP 8889 (WAN) > NAT > TCP 80 192.168.10.6 (my webserver)
-
doesn't matter what you listen on locally!!! If it never gets to your wan then it can not forward it - PERIOD!!! Not rocket science here ;)
Are you pinging me
