[Solved] I'm apparently unable to port forward...
-
-
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
-
https://i.imgur.com/bEfo0vQ.png
-
Seem you got ISP issues...
Run your continue ping -- while I sniff... And show you that I am answering..
-
here - I am answering you!!! IF you not getting it that is on your ISP..
-
I'm gonna shutdown pfSense and switch to Mikrotik to try something..
-
And your IP will change! Or you MAC will change - etc etc..
What part do you NOT get about pfsense not seeing traffic it can not FORWARD?? Pfsense has no control of what hits is interface or not... Is pfsense a VM? Or hardware?
Here is where trace stops
inetnum: 177.126.96.0/20
aut-num: AS16735
abuse-c: CST87
owner: ALGAR TELECOM S/ATracing route to 187.73.x.x over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.9.253 2 12 ms 9 ms 8 ms 50.4.132.1 3 9 ms 8 ms 9 ms 76.73.191.106 4 10 ms 10 ms 9 ms 76.73.164.121 5 9 ms 12 ms 17 ms 76.73.191.140 6 11 ms 10 ms 9 ms 76.73.164.105 7 11 ms 13 ms 20 ms 76.73.164.65 8 16 ms 12 ms 12 ms 76.73.191.224 9 12 ms 12 ms 12 ms 75.76.35.10 10 34 ms 35 ms 33 ms 75.76.84.231 11 31 ms 32 ms 31 ms 75.76.35.105 12 179 ms 178 ms 190 ms 198.32.160.236 13 178 ms 180 ms 181 ms 200.150.1.169 14 193 ms 176 ms 178 ms 200.150.10.1 15 177 ms 176 ms 177 ms 177.126.100.153 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. -
it's hardware.
-
This post is deleted! -
This post is deleted! -
Dude don't worry about it - but Pfsense can not forward what it can not see!!! Period.. If pfsense is not seeing the traffic - then its hardware related or something upstream is blocking it.. Pfsense can not forward what it doesn't get, you can not see an answer to your ping if it doesn't get there..
Did you change it what is your IP now?
Is this your ISP?
ALGAR TELECOM S/A -
@ninom4ster said in I'm apparently unable to port forward...:
am like that.. I want things to FUCKING WORK.
I don't want to debug anything.Nice.
If the traffic does not arrive on WAN there is nothing for the firewall to forward.
You are going to have to figure out what is going on upstream preventing that traffic from being sent to you. When you have debugged that, your port forward will work. Sorry that maintaining a network is sometimes work. Good luck with your ISP.
That packet capture is before rules, before snort, before everything. The connections from the outside are not arriving on WAN.
