-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
nfdump with geodb, nfprofile and nfsen - profile issue #557
Comments
Yes - nfprofile does not use the geoDB, as the original design was the enrichment of the nfdump output. The additional purpose to use it for AS filtering was implemented later. The same is true for the torDB. |
that sounds great! If you need a tester, I’m happy to help. thank you! |
I was wondering about profiling tor. Thanks for the confirmation that I too can see some use cases around geo and tor data in profiles and maybe even augmenting data at capture. This seems like a good topic for discussion and I'm sure you, Peter, have spent some time thinking about it. I'd like to discuss it further but a PR doesn't seem like the right place. |
I implemented a first poc for geo and tor filtering in |
@brownej Feel free to open a new issue to discuss this topic. |
Nice to hear it works! |
Hi,
I'm having trouble getting the GeoDB feature working with profiles in NfSen. I have added the path in the
/usr/local/etc/nfdump.conf
file:The directory looks like this:
In the live profile, I can see that enrichment is working:
However, my custom profiles with AS filters are not working. The nfcapd files are all empty:
And here's the directory structure for the custom profiles-data:
logs:
Screenshots:
Should this work with GeoDB enrichment in NfProfiles? If so, do you have any idea what might be going wrong?
Systemspecs: Ubuntu 24.04 (container)
nfdump: 1.7.4 with sflow nfpcapd maxmind nsel nfprofile nftrack ja4 readpcap ftconv
nfSen: 1.3.10, nfdump: 7
php: 8.3.6
apache: 2.4.58
Netflow exporter: freertr with dpdk dataplane
Thank you for the excellent work you're doing!
BR
Takalele
The text was updated successfully, but these errors were encountered: