This is working very nicely, thank you. Also, I upgraded to 0.11.0 this morning and that seems to have gone well.
Which SQL options (such as sql_optimize_clauses) should be applied to each plugin, and which ones can I apply globally? I looked through CONFIG-KEYS but the flags aren't listed for SQL options. For the meantime I have declared a number of settings both globally and per plugin to get the best performance. sql_optimize_clauses: true sql_optimize_clauses[in]: true sql_optimize_clauses[out]: true Thanks! -Matt At 6:34 PM +0100 9/21/06, Paolo Lucente wrote: >Hi Matt, >your actual setup sounds very reasonable for what you want to do. >About the chance of filtering out some traffic, in your case ICMP >datagrams, you can use Pre-Tagging. > >1. create a new Pre-Tagging file (if you are not already using >one for other purposes), say pretag.map; insert into it a line >like the following: > >id=100 ip=<NetFlow agent IP address> filter='ip proto 1' > >The above line associates the tag '100' to each packet matching >the filter 'ip proto 1' (ie. all ICMP packets) coming from your >NetFlow agent (in your case, it's the Packeteer Packetshaper). > >2. link your Pre-Tagging file into your nfacctd configuration: > >pre_tag_map: /path/to/pretag.map > >3. attach a negative Pre-Tagging filter - matching tag 100 - in >your nfacctd configuration: > >pre_tag_filter[sql_instance_a]: !100 >pre_tag_filter[sql_instance_b]: !100 > >To be even more correct, because one of the two instances should >be accounting incoming traffic, you can stick the filter only to >that. > >Cheers, >Paolo -- Matt Richard Access and Security Coordinator Computing Services Franklin & Marshall College [EMAIL PROTECTED] (717) 291-4157 _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
