Hello Nitzan, On Mon, Dec 05, 2005 at 07:51:46PM +0200, Nitzan Tzelniker wrote:
> 1. flow-nfilter has configuration file where you define filter > primitive and filter definition and then in flow-report you only call > the filter definition and don't need to specify the all filter over > and over. No, actually there aren't chances to define complex primitives (e.g., match this and that, match this but not that, the default behaviour is this, etc.) and then recall it. However this could be a nice idea for the future. I'm inserting it into the todo list. > 2. in flow-tools you can filter by source/destination interface and > exporter address directly and you keep the flow-tag for other things > but in pmacct you can`t filter by these fields and you must use > pre_tag_filter for these common filter fields. Right. 'pre_tag_filter' is aimed to add filtering capabilities to tags. If the flow passes the filter, you will still have the tag available for other uses (e.g., post-processing). What you will not be able to do is to assign tags "incrementally", for example: 1st rule: match conditions; then assign tag A 2nd rule: match conditions and match tag A; then assign tag B etc. Are you facing a problem that requires (or would benefit from) such handling ? If this is the case, can you briefly describe/illustrate it ? It may help in taking the right development direction. Cheers, Paolo
