One big ruleset
-
I messed up a little my firewall (I think, I reverted 40+ snapshots) and I had to redo part of the ruleset.
The good thing is that I have to delete, not add rules, so it's relatively fast. The bad thing is that it's relatively fast.
I've been in the opposite scenario many times too; the more dreaded one of splitting a transit network into discrete interfaces, and I've always wondered why don't ↓ this ↓ exist:
I've meant to suggest it several times but I've been obviously much more busy and by the time I'm finished, I've forgotten about it. And, all the work is already done, you just add another table the PHP templates and maybe add closer buttons each section, or another set at the top or move them and have them floating on the side like DokuWiki does.
All in one page is not as aesthetic, but it's immensely practical and it could be just an option, not the norm.
Though if we're wishing for options, parsing a CSV for DHCP reservations would top my list. A saw I think in FusionPBX, you can add any CSV file and tell it in what order to take the values. I mean… CLIs do it all the time, but web GUIs not so much.
So…I guess that's it.
Sidenote: Have you noticed tables don't align the same one page to the next? That screenshot is doctored kind of a lot to look sort of normal. I noticed just now because the window frames did align perfectly.
-
So you would like to see a single page firewall view because that would enable drag-and-dropping a selection of rules between interfaces?
Steve
