You're on the right track. It's definately not an easy task since the data storage has to change. A lot of fun will also be presented when you dive into the code for the row helper :)
Scott On 12/28/05, Joshua Coombs <[EMAIL PROTECTED]> wrote: > Ok, first look at this say I'm in over my head, php isn't as easy for > me to tackle as perl just yet. > > The XML for aliases is currently: > > <aliases> > <alias> > <name>Netblocks</name> > <address>192.168.0.0/17 10.10.0.0/19 172.168.16.0/24</address> > <descr>Netblocks of questionable value</descr> > </alias> > </aliases> > > The php for the aliases interface manually parses the address string > to pick out individual entries. This explains why there aren't > descriptions for each entry in an alias, as that would make the parser > work excessively hard, and would likely be prone to failure without > restricting allowable chars excessively. > > <aliases> > <alias> > <name>Netblocks</name> > <address> > <data>192.168.0.0/17</data> > <note>Bob's sandbox</note> > </address> > <address> > <data>10.10.0.0/19</data> > <note>Production LAN</note> > </address> > <address> > <data>172.168.16.0/24</data> > <note></note> > </address> > <descr>Netblocks of questionable value</descr> > </alias> > </aliases> > > This bloats out the xml, but gives a clean way of adding descriptions > for individual entries. It would also require tweaking the backend to > get it to pump out configs to pf correctly, something I was hoping to > avoid initially. (And I have yet to stumble across that piece of > code, so I've no idea how much work it will be to manipulate.) > > If noone has any objections or other suggestions, this is what I'll > try to impliment. > > Joshua Coombs > > >
