GUI accessible, can't block webgui access on all interfaces, unless WAN

[Bognad]

I have configured web access on 8087 port, disable antilockout rule.
I have created some rules to reject acooections on 8087 port, but i have access to webgui via interfaces. I have no packets in packet counter.

[Gertjan]

None of your firewall rules are used.
You're hiding the interface, but I guess it's not the right one.

edit : if your placed these rules on the "Floating Interface", you should set the Quick option ( see https://docs.netgate.com/pfsense/en/latest/firewall/floating-rules.html for how to use floating rules ).

[Bognad]

Thanks for answering.
I do not use floating rule.

[Gertjan]

I used this rule to test :

The PC I'm using right now has 192.168.1.6.
When I activated the rule and reset firewall states ;) , I could not access pfSense any more. I had to use another PC - not being 192.168.1.6 - to gain access again.

Btw : hiding interface names ? Why ? They are just name tags.

[Bognad]

@Gertjan
hiding interface name... bcz i am paranoid)

[johnpoz]

@Bognad said in GUI accessible, can't block webgui access on all interfaces, unless WAN:

bcz i am paranoid)

An interface name?? Wow!! Lay off the drugs dude!

Keep in mind if there is an existing state, that would allow.. When you create block/reject rule - you need to flush any existing states that rule would of blocked. States are evaluated before rules.

[Gertjan]

@Gertjan said in GUI accessible, can't block webgui access on all interfaces, unless WAN:

When I activated the rule and reset firewall states

=>

Check the box and hit reset.

[johnpoz]

Or you can just find the specific state or states in the table and kill it/those. But sure a full flush works too ;)