Hi Brian, I've just reproduced in lab the configuration you mention, ie. selective teeing (or tee plugin in conjunction with tee_transparent, pre_tag_map and pre_tag_filter), and it works OK to me: A -export-> B:2100 -tee-> A:2101.
Just in case below you find a sample configuration: .. plugins: tee[a] pre_tag_filter[a]: 100 tee_receiver[a]: X.X.X.X:2101 tee_transparent: true ! pre_tag_map: /path/to/pretag.map .. Then in pretag.map: id=100 ip=X.X.X.X I did also perform the counter-test that changing id to 101 it does not export anything anymore. A couple other points are addressed below in-line: On Sat, Oct 27, 2012 at 09:45:09AM -0500, Brian Talley wrote: > One of these would utilize mysql plugins and one would utilize the memory/ > imt plugin. (If there's a way to combine these in the same nfacctd process, > I'd be interested in that as well.) Sure, you can combine multiple plugins - even of different type - within the same nfacctd instance. You have to name plugins (ie. a, b) and attach directives to each (specifically by recalling the name or globally), ie.: .. plugins: memory[a], mysql[b] ! ! Global config directive, applies to a, b aggregate: .. ! ! Specific config directive, applies to a pre_tag_filter[a]: .. imt_path[a]: .. .. ! ! Specific config directive, applies to b pre_tag_filter[b]: .. sql_table[b]: .. .. > Also, as it relates to the scenario described above, would there be any way > for both tee'd instances to reference a single BGP thread? Can you elaborate more on this? Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
