I have the same problem with the 2.4.2 in the french WebGui. The Gateway list is empty. But it works well in English WebGui. Try to change language in System/General Setup.

I couldn't help but notice no one has acknowledged this in redmine as an feature/issue. Is this, will this get acknowledged?

Problem solved with 2.4.2**-RELEASE-p1** version 8)
Good job PfSense team.  ;D

Add the following in Additional RADIUS Attributes (REPLY-ITEM) Class := admins

@KOM:

i dont know is it possible, if ya how can i do it.

I don't know.  That looks more like a development question, not pfSense specific, and it may be outside the scope of these forums.

thanks, i solved the Problem. there is two solution:

i could use tcpdump to see all the traffic including data which i send from my Computer. using tcp socket

finally i choosed second way, wrote a tcp socket as Server in c and execute it from console. Now i can send commands through tcp to second System (my Gateway) with some Parameters and execute the Shell script with These parameters.

Hey look at that!  It works!

Thanks so much Gertjan!!

@johnpoz:

Pretty sure that is the default… Do you have this checked or not checked? Under System Advanced..

Enable webConfigurator login autocomplete
When this is checked, login credentials for the webConfigurator may be saved by the browser. While convenient, some security standards require this to be disabled. Check this box to enable autocomplete on the login form so that browsers will prompt to save credentials (NOTE: Some browsers do not respect this option).

I  have now checked this settings and disabled autocomplete , chrome is not offering to save password now but Mozilla still does.
Thanks  for your help.

I don't think so, but let me check

For future

Putty>>Restart Web Configurator

I had a similar issue once and this fixed it

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.