Acces WebGUI from Wan issue.
-
If you turned off block rfc1918 and are access it from your internal network wan side should have no problem if you allow the correct port. Looks like you have states there that are established..
-
Block RFC1819 is turned off.
But as you can see on the printscreens the rule seems to work it says ESTABLISHED.i really don't get it.
-
Sniff on your wan side when making the the connection.
-
This is what i get, does this means something to you?
https://imgur.com/a/wQz1xp5
.10 my pc .75 wan ip of the pfsense.
-
Yeah nothing answered... Where did you sniff that at? On pfsense Wan?
You should get syn,ack back when you send a syn.
-
Yes i ran Wireshark on my pc 192.168.0.10 is that the good way to do so?
-
Doesn't show you if pfsense actually saw the traffic.. I would sniff on pfsense wan at same time.. Does pfsense send syn,ack but your clients just not seeing it.
You say this is all VM network right - that would be my guess where your problem is!!!
-
I just did it on the PfSense side and it sees the request and sends an ack.
-
Have you tried to clear Browser cache and/or Incognito Window?
When you open SSH on WAN side, is the connection working?-Rico
-
Yes i did have tried from other pc's also but same result.
I just launched an SSH from 192.168.0.10 to .75 (PfSense Wan) and captured from PfSense.
-
@ptibiskwi said in Acces WebGUI from Wan issue.:
I just did it on the PfSense side and it sees the request and sends an ack.
No it didn't - it answered an arp request, from your pic it is not sending back anything.. All I see it traffic to 443, no response from 443.
Same with your ssh - no response, just an answer to the arp request.
Did you edit your wan rules to allow ssh? What is in your floating rules if anything?
edit: Do you have any sort of port forwards that might be forwarding those ports or floating rules that would block them? You sure your rules loaded? Once you allowed the port?
