Parse errors on ampersand in remarks

Same thing for characters: < , (

Presumably would've choked on > and ) had it reached that far. I don't see any periods in use within remarks, at least in this config, so I don't care about that one...

Yah, this is a gonna be hairy to resolve in the RACC parser and lexer. I bet people have all kinds of characters there that are not allowed elsewhere in PIX configs. Once I get that fixed then I'll have to filter them out in the Flint::CiscoFirewall code that builds a model of access lists.

Congrats on being the first person to use remarks in a config that I've seen in a couple years!

I'm not using them myself, but my four network admins do quite frequently. We're probably in the 15k-line range for our primary data center firewalls, and 10k for secondary. This is only one zone, but we use things like -Inside and -Outside in templates for the setup of new systems and zones. Impossible without remarks.

I'll grep out all remark lines and see what I get after that.

Ok, Flint will churn on those for awhile. We were testing with 5k line configs and found it running about 5 minutes from start to finish. There is not very good UI feedback when running a large ruleset right now, so you'll get a spinner.