Quoting Joseph L. Casale (from 24/08/10 04:23): >> You can export a configuration file to see the file structure, build >> a configuration backup that has the aliases in it based on the sample, >> and then restore your "backup". That's what we did. > > That’s a good idea, but the lists need updating and something scriptable > would be easier so I could do this at the cli less obtrusively...
You can make some nice scripts with xmlstarlet (http://xmlstar.sourceforge.net/), and automate additions to the configuration from there; but there will always be some interruption when you reload in order to get the new config. Perhaps there's another way; what are you doing this for? Instead of basing rules on a large set of aliases that you have to update regularly, is there some other characteristic you can group your rules by? (AKA 'describe the original problem, not just the one step you're stuck on') -jim --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
