-
Notifications
You must be signed in to change notification settings - Fork 349
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
Allow changing NDPI configuration when using PF_RING FT to to disable dpi guess on giveup #965
Comments
In order to handle this, FT provides the ability to set an external ndpi handle which can be customized/configured by the user. In order to use it, just remove the PFRING_FT_TABLE_FLAGS_DPI flag in pfring_ft_create_table, created a ndpi handle, and provide it to FT with pfring_ft_set_ndpi_handle just after pfring_ft_create_table. Example: ` pfring_ft_table *ft = pfring_ft_create_table(0, 4000000, 0, 0, 0); |
@cardigliano , So I can use it already in the current version, right? |
Correct |
@cardigliano , it did not work. I used the attached PCAP , port 88 that is the default kerberos port and it still gave me KREBEROS although it does not contain kerberos data. |
I pushed an update which introduces a new PFRING_FT_TABLE_FLAGS_NO_GUESS flag for pfring_ft_create_table. This allows you to avoid the external ndpi handle. Please see ftflow_pcap.c as example (e.g. ftflow_pcap -i ~/krb_null.pcap -7 -N) |
@cardigliano |
The patch is in pf_ring, however you always need to get both of them updated |
FT can return the nDPI handle with pfring_ft_get_ndpi_handle(table) on which you can call ndpi functions, however calls like ndpi_set_config(handle, NULL, "dpi.guess_on_giveup", "0") should be called before the ndpi handle is finalized. This means we have to extend the FT API to allow that: ndpi_set_config() must be called before ndpi_finalize_initialization()
The text was updated successfully, but these errors were encountered: