mirror of
https://github.com/vel21ripn/nDPI.git
synced 2026-05-02 00:40:17 +00:00
efccc7d5e4
Right now, there is, in essence, a static mapping between flow protocols and flow breeds. Make it dynamic: allow to have different flows, with the same classification but differents breeds. This is the same logic that we already have for categories.... Preliminary work to support breed in category lists. API change from the app POV: to get the flow breed don't use anymore `ndpi_get_proto_breed()`, but access directly `struct ndpi_proto->breed` The functions `ndpi_domain_classify_*()` and `ndpi_get_host_domain_suffix()` now have a `u_int32_t` parameter as `class_id` (instead of `u_int_16_t`), with the following logic: ``` class_id = (breed << 16) | category ``` instead of the old: ``` class_id = category ``` Please note that this change is back-compatible: if you are not interested into breeds, you don't need to update the application code. |
||
|---|---|---|
| .. | ||
| bittorrent.pcap.out | ||
| bittorrent_tcp_miss.pcapng.out | ||
| forticlient.pcap.out | ||
| http-basic-auth.pcap.out | ||
| http-pwd.pcapng.out | ||
| http_auth.pcap.out | ||
| ookla.pcap.out | ||
| sip.pcap.out | ||
| teams.pcap.out | ||
| tls_1.2_unidir_client_no_cert.pcapng.out | ||
| tls_1.2_unidir_server_no_cert.pcapng.out | ||
| tls_1.2_unidirectional_client.pcapng.out | ||
| tls_1.2_unidirectional_server.pcapng.out | ||
| tls_1.3_unidirectional_client.pcapng.out | ||
| tls_1.3_unidirectional_server.pcapng.out | ||
| tls_ech.pcapng.out | ||
| tls_verylong_certificate.pcap.out | ||