Require State Filter setting breaks filter rule link to associated states
If one configures
System > General Setup
- Require State Filter -> yes (enabled checkbox)
that's a great way to stop browsers (like firefox) to crash or load infinitely while opening "Diagnostics > State" on a busy firewall.
We had to set this as on our busy datacenter cluster there were so many state that most browsers were going down while trying to load the state table page unfiltered.
But: with the above option set, the cross-linking of states belonging to filter rules is no longer working:
- enable "Require State Filter"
- go to "Firewall > Rules"
- click on the States in front of a busy firewall rule that you want to check
- you are redirected to diag_dump_states.php but the page thinks that your call is "unfiltered" therefore not showing anything
This behavior can be found up until the latest 2.4.5 RCs.
Is it possible to "rewrite" the call from the filter rules page, that it shows the states for that rule but leave the general "require state filter" in place so nobody accidentally crashes its browser entering diag_dump_states.php without filtering? Perhaps filling out the corresponding fields when jumping to the page? I know, no game-breaking bug, but a little annoying one as it robs us of a valid diagnostic/debugging tool and linking to states in firewall rules becomes obsolete.