After further research, I found that all IPv6 traffic exported by this
router is being misinterpreted by nfdump/nfsen as IPv4 (and
misinterpreted IPv6-traffic flow records enter the system in a state of
total "junk").
It does not seem to be a problem of my setup because IPv6 traffic flow
records exported from another device (an ASA 5525) are read in the right
way.
Export of data is correct, and Wireshark is reading flow records
properly (after configuring data to be decoded as CFLOW) but nfdump does
not treat the data correctly.
Note: For your reference, IPv6 netflow data is collected using the
following setup on the router:
flow record ipv6_record_cisco2
match ipv6 destination address
collect ipv6 protocol
collect ipv6 source address
collect transport source-port
collect transport destination-port
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last
!
Please help to overcome the issue.
Thanks,
Nick
On 30/7/2016 2:17 μμ, Nikolaos Milas wrote:
> *They are records referring to IPv6 traffic, misinterpreted as IPv4.*
------------------------------------------------------------------------------
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
