A seperator might make sense. But grouping and hiding rules is a bad idea based on my experience.
A tree structure that is allways collapsed is annoying when you need overview of all rules. And defaulting to a expanded look will just act as a seperator. Imho interface tabs acts as grouping enough. And a seperator line on floating rules might make sense in some cases. If one would implement a rule type called "seperator", it could be highlighted in the view based on its type. I believe that all rules affecting a interface should be seen in plain view. To me this smells like you whish for "over engineering". Just my 2cents. 10. feb. 2015 22:10 skrev <[email protected]>: > > On 02/10/2015 07:04 PM, Christoph Hanle wrote: > >> On 10.02.2015 14:44, [email protected] wrote: >> >>> Hi, >>> >>> Is there any possibility to create "groups" or otherwise have seperators >>> between rules on the firewall page? Basically what I'm trying to do is >>> make it easier to see which rules are "connected" could be based on host >>> or service. So it would be nice to have some sort of visual seperator to >>> create a "group". >>> >> Hi KP, >> I am doing this by creating disabled rules and have as description the >> description of the next rules. To differ from real disabled rules a -> >> at the end if helpfull. >> >> not the perfect seperator, but a doable workaround >> >> >> bye >> Christoph >> >> Hi, > > A bit disappointing, but at least I wasn't just blind :) > > What I was hoping for was like a horizontal separator across the whole > table, maybe even a way of expanding / collapsing a "group". > > -kp > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold >
_______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
