Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ntopng showing no IPv6 traffic flows/IPs/etc using IPFIX #1906

jforman opened this issue Aug 9, 2018 · 2 comments

ntopng showing no IPv6 traffic flows/IPs/etc using IPFIX #1906

jforman opened this issue Aug 9, 2018 · 2 comments


Copy link

@jforman jforman commented Aug 9, 2018

I've recently spun up IPv6 connectivity on one of my subnets at home through a tunnel broker, and wished to use nprobe/ntopng to dig into traffic flows and learn some things. I set up a flow exporter on my firewall/router to send traffic to an nprobe collector on another internal host, be viewed via ntopng. The problem is, nowhere in the ntopng UI does it show any IPv6 flows/traffic. Every IP/flow/etc is IPv4. I must be missing something in my configuration....

OpenBSD 6.3 is exporting data (as my firewall/router):
$ cat /etc/hostname.pflow0
flowsrc flowdst flow1:3001 pflowproto 10

nprobe on flow1 host:
nprobe --zmq "tcp://*:5556" --collector-port 3001 --collector none --interface none --flow-version 10

ntopng on flow1 host config:
root@flow1:~# grep -v ^# /etc/ntopng/ntopng.conf

ntopng Community Edition v.3.5.180808
nprobe: v.8.5.180808 ($Revision: 6242 $)

Copy link

@jforman jforman commented Aug 9, 2018

It seems the template via -T was not defined, and from reading ntop/nProbe#169, i was able to get it working. Why doesn't this work by default? Are there different forms of templates?

Copy link

@simonemainardi simonemainardi commented Aug 10, 2018

We use a conservative approach and leave the default templates as small as possible, to avoid exporting fields default users don't care about. This is not a loss in generality as templates are fully customizable and any advanced user can tailor them to fit his/her needs.

In the case of IPFIX the default template is IPv4 only and contains the following fields and this explains why you were not seeing IPv6:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants