pfsense, web server and VLAN's
-
@stephenw10 Ok, I am getting offline and 100% packet loss on my Gateway.
No traffic is getting through to Web Server either, I thought it might have been my software firewall on web server CSF. I disabled it and still nothing!
-
@rockyuk said in pfsense, web server and VLAN's:
I am getting offline and 100% packet loss on my Gateway.
Which gateway - how are you posting here if your internet is down? Nothing could get to pfsense wan if its gateway is down..
There should only be a "gateway" set on your actual internet connection "wan"
-
It works for me. Traffic to that IP is being forwarded to a webserver. I see:
Is that not correct? How are you testing?
Steve
-
@stephenw10 I have switched it back to my normal connection I can't leave it on the Firewall as it is not resolving. So i have to switch between the two to keep my Web Server up.
-
Mmm, Ok well nothing is going to work incoming whilst the gateway is down.
I assume it was up earlier? What changed?
-
@stephenw10 I still get internet even when it is down which is weird. But i am wondering if it is that which is causing the routing issue with the server?
I don't think it ever came online, even when it says it is offline I still manage to get internet access.
-
What is the gateway? It may not respond to the monitoring pings.
Try editing it in System > Routing > Gateways and setting an alternative monitoring IP like 8.8.8.8.
-
@stephenw10 Ok, adding the 8.8.8.8 to the Gateway worked for keeping that up now. I have done a quick packet capture on the WAN and Web Server Interface which i zipped up a PDF file below.
STATES
ROUTES
The gateway that was provided by my ISP does not seem to be coming up on pfsense and it is pulling in it's own DNS servers from my ISP. Not sure if that will cause an issue but it is not what i have on my current setup. The traffic is not being routed from WAN to Web Server interface and i can't understand why.
-
Hmm, some conflicting results here.
The state table shows traffic being correctly sent to the webserver but there are no replies shown on any of those states as though the server is refusing the connection.
The WAN pcap doesn't show any inbound traffic on port 443 at all. It on;y covers ~4s though you probably need to filter by the external IP you're testing from.
The WEBSERVERS pcap shows successful two way traffic to the server though:
10:45:02.447710 IP 82.132.215.99.49926 > 192.168.0.100.443: tcp 0 10:45:02.447879 IP 192.168.0.100.443 > 82.132.215.99.49926: tcp 0 10:45:02.458748 IP 82.132.215.99.49926 > 192.168.0.100.443: tcp 517 10:45:02.459162 IP 192.168.0.100.443 > 82.132.215.99.49926: tcp 0 10:45:02.461764 IP 192.168.0.100.443 > 82.132.215.99.49926: tcp 1356 10:45:02.461868 IP 192.168.0.100.443 > 82.132.215.99.49926: tcp 384 10:45:02.473285 IP 82.132.215.99.49926 > 192.168.0.100.443: tcp 0Steve
-
@stephenw10 Do you think it is the server rejecting it then? I disabled the software firewall on it and still was not passing to it. I will try a quick test now by disabling the software firewall on it and do another packet trace.
-
It could well be. The states showing it not responding are from different external IPs that in the pcap where it is.
-
@stephenw10 I have just done two things, I have disabled the firewall on the web server and when i checked the VDSL Modem it had two live Bridge connection. I have removed one of them and it appears that the server is now up and running. But i still cannot test from internal network?
-
How are you testing? If you want to be able to access it via FQDN you need to enable either split-DNS or NAT reflection as shown in the link I posted above.
Steve
-
@stephenw10 That's all working now. Thank you very much for your patience and help
-
No worries, glad you're up and running.
