> <rule> > <action>DNAT</action> > <source>net</source> > <dest>loc:10.0.0.1</dest> > <proto>tcp</proto> > <port>80</port> > <mark>88</mark> <!-- this is the line that makes it simpler --> > </rule> > <!-- also, reading this in a console is a lot more intuitive when you > come back > 6 months later than an ass-ton of columns with no header information > (because > it's three page-ups away, not because it's deleted, obviously --> > Introducing the xml format into Shorewall would be the most hideous thing to do imo! I can't see a single benefit from this at all.
Shorewall is most commonly used on machines without shiny guis or even graphics cards, so I can't see these files being processed by the gui tools suggested or having network admins falling themselves over to get the latest xml tool to read those config files, because, lets face it - without a proper tool to see the different options one could easily get lost in all the markup. The best thing, as already suggested in this thread, is to keep the existing format, with maybe introducing the few vim improvements - that would be good. My two pence worth, of course! ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
