Scratch that, it was me being silly.
The Flow lifetime values are set quite high in our setup, so I was
expecting to see data before it was sent, also I had a syntax error in
my pretag.map (it's amazing what a fresh set of eyes will pick up)
Cheers all the same :)
Peter Adkins wrote:
Hey all,
I'm looking to use the nfacctd's pre-tagging map to differentiate
traffic type to customers. Currently, if a customer downloads data
from a certain IP range, it gets marked in the database with a given
'agent_id', in order to differentiate between what data went where.
This works fine, however, in the lab I have had this working with a
single NetFlow generator (NAS) with a list of IP ranges in the pretag
map. In the real world, this will need to work over multiple NAS, with
the same IP ranges. For example:
-----------
pretag.map
-----------
id=1 ip=xxx.xxx.xxx.1 filter='src net 1xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.1 filter='src net 2xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.1 filter='src net 3xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.1 filter='src net 4xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.2 filter='src net 1xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.2 filter='src net 2xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.2 filter='src net 3xx.xxx.xxx.xxx/xx'
id=1 ip=xxx.xxx.xxx.2 filter='src net 4xx.xxx.xxx.xxx/xx'
----------------------
nfacctd_sql.conf
----------------------
...
pre_tag_map: /usr/local/pmacctd/conf/pretag.map
pre_tag_filter[reserved]: 1
...
When I try this, the data does not get the agent_id added. If I only
have one NAS listed in the pretag.map file, then it works again.
What am I doing wrong? Cheers :)
-- Peter
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
