I think the following option on the interface is enable and you are coming from an internal ip address. "Block private networks and loopback addresses"

Indeed, that works - thank you! I had thought I'd need to apply changes to the rules by running /etc/rc.filter_configure via ssh, but this is even simpler.

That was something I searched and played with a couple of months ago. Not sure why this isn't the default.

I agree with johnpos. It would help to neaten up, particularly when you create a multitude of additional VPN interfaces

"It's like it reordered the firewall rules and locked me out." There is a specific rule to prevent that - the antilockout rule that allow the port the gui listens on and the ssh port.. Did you disable this rule? Did you create a rule in floating that happens before interface rules that overrode the antilockout rule?  Are you coming from a different network and not the lan network that doesn't have the antilock out rule?

Ok, so using the console I reset back to the factory configuration and was able to access the Web Configurator again.  Then I uploaded my previous configuration and things are back up and running.

Why would you think there is a rule for the tunnel interface?  You would never hit that address.. You might hit the ipv6 address you put on your lan, but why would you ever be hitting the transit IP?  That is in the tunnel??

May be related: https://forum.pfsense.org/index.php?topic=141600.0

No the gateway is on the WAN but its in a data center so its a gig connection to a device in the same building. But thats kind of the same thing you mentioned  of being a lan. In the other data center we have 2.2.6 and we are seeing real numbers like as in .6ms and it matches the ping when done. so that does not match this behavior.

How about hitting that "Display Advanced" button first.

@xpxp2002: …. How do I go about formally reporting this to investigate/get into the bug queue? Go here pfSense Forum » pfSense English Support » webGUI and read this thread Typo error.

Ideally, a PR on Github is best. Tickets on Redmine are OK as well. Main problem with posting these on the forum is that they're easy to miss.

@wizencrowd: For a school project I need to configure a server with pfsense. We want to use it as a captive portal. My problem is that I can't get in the WebGUI when I have my Wan connection plugged in. What ?? (but you explain why afterwards …) When I freshly booted my server I need to unplug the wan cable, then I can login in pfsense. After that I can plug the wan cable back in an everything works. Do you guys now How i can fix this? When I booted the server I don't have internet, but when I login in pfsense I get internet. @wizencrowd: Some info that might be usefull: Lan IP : 192.168.1.100 Wan IP : 192.168.1.103 (DHCP) Thanks for the info. You totally broke one of the most important rules when it comes routing. KEEP LAN on 192.168.1.1/24 Make WAN something 192.168.2.1/24 or 10.0.0.1/16 but NOT in the 192.168.1.1.1/24 segment. IF your WAN needs to be in 192.168.1.0/24 then make your LAN (example) 192.168.2.1/24 Remember : your are operating a router/firewall, not a switch.

Ok. Thanks.

Trying to get this to work on 2.4.2 but all I'm getting (using jimp's lines, adapted with my own credentials and addresses) is the php page again: it downloads the download php page. It creates the cookies and csrf files but no backup xml file. Doesn't matter which user I use (admin or dedicated backup user). Fiddled around with the password (for testing now only using a simple word with no fancy characters). Wget doesn't generate any errors (because from its point of view everything is ok). Any suggestions?

Thanks! Perfect :) Much appreciated