For archives: this is now fixed and tested working by Gregoire: http://www.mail-archive.com/pmacct-commits@pmacct.net/msg01035.html
Cheers, Paolo On Fri, Mar 21, 2014 at 05:52:59PM +0000, Paolo Lucente wrote: > Hi Gregoire, > > Thanks for reporting this. It smells like a bug. Can you please produce > and send me privately a trace with some NetFlow packets containing NAT64 > entries so to be able to reproduce/fix in lab? > > Cheers, > Paolo > > On Fri, Mar 21, 2014 at 05:41:12PM +0100, Grégoire Leroy wrote: > > Hello, > > > > I'm using an ASR1001 Cisco for CGN (NAT444 and NAT64). The ASR1001 > > sends logs with netflow and I can read it with the method described > > here (http://wiki.pmacct.net/OfficialExamples), section 17. To read > > them, I use pmacct 1.5.0RC2 (in fact, nfacctd). > > > > For NAT444, everything is good, I got records as : > > 100.96.0.10 58776 [PUB_IP_1] > > 18782 2 2014-03-21 17:14:53.651000000 0 > > 0 > > > > However, here is what I get with NAT64 : > > 0.0.0.0 51056 [PUB_IP_2] > > 1029 2 2014-03-21 17:14:53.574000000 0 > > 0 > > > > I should get an IPv6 address instead of "0.0.0.0". > > Note : I've built pmacct with --enable-ipv6 > > > > Do you have any hints about it ? Did I miss something ? > > > > Thank you very much, > > Regards, > > Grégoire Leroy > > > > _______________________________________________ > > pmacct-discussion mailing list > > http://www.pmacct.net/#mailinglists > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
