Hi Rob, To confirm that: what you are verifying is not the intended behaviour & what you describe as your understanding is the intended behaviour instead.
It would help to know if you have prefixes as part of your aggregation; if yes, whether they are also zeroed out if not in the networks_file or not. Meanwhile two tests: * add 'nfacctd_net: fallback' to your config * make sure 'networks_file_filter: true' is not set in your config If none of this helps out, can you please post (here or privately) your config so that i can try to reproduce this in lab? Cheers, Paolo On Fri, May 22, 2015 at 09:09:30PM +0100, Rob Greenwood wrote: > Hi, > > We’ve got nfacctd running, collecting IPFIX data from a number of Juniper MX > routers and exporting it into ElasticSearch successfully. > > Our iBGP prefixes have their AS in the netflow data as AS0. I’m trying to > override this by placing our prefixes into a networks.lst, and specifying the > following config: > > networks_file: /opt/pmacct/etc/networks.lst > nfacctd_as_new: fallback > > >From reading the documentation, this should allow me to override prefix ASNs > >from within the networks.lst, but would then fall back to pulling the ASN > >from netflow if the prefix doesn’t exist in network.ls. > > However, the behaviour I’m seeing is that the ASN for my prefixes is being > set correctly, but now every other non-matching network is set to AS0. > > Is this intended behaviour? > > -Rob > > > -- > DataCentred Limited registered in England and Wales no. 05611763 > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
