nDPId/schema
Toni Uhlig 19036951c7 bump libnDPI to 1216ec6a2719408a487f696f5b601bdb9eec727d
* incorporated upstream API changes related to detection protocol bitmasks
 * added missing flow detection categories

Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
2025-09-09 12:05:26 +02:00
..
daemon_event_schema.json bump libnDPI to 1216ec6a2719408a487f696f5b601bdb9eec727d 2025-09-09 12:05:26 +02:00
error_event_schema.json Initial tunnel decoding (GRE - Layer4 only atm) (#55) 2025-02-25 15:17:16 +01:00
flow_event_schema.json bump libnDPI to 1216ec6a2719408a487f696f5b601bdb9eec727d 2025-09-09 12:05:26 +02:00
flow_events_diagram.drawio Improve README 2022-09-19 17:23:11 +02:00
flow_events_diagram.png Improve README 2022-09-19 17:23:11 +02:00
packet_event_schema.json Added vlan_id dissection of the most outer (first) 802.1Q header. Fixes #50 2024-11-02 15:48:45 +01:00
README.md Replaced ambiguous naming of "JSON string" to more accurate "JSON message". 2023-12-04 13:01:27 +01:00

schema

All schema's placed in here are nDPId exclusive, meaning that they are not necessarily representing a "real-world" JSON message received by e.g. ./example/py-json-stdout. This is due to the fact that libnDPI itself add's some JSON information to the serializer of which we have no control over. IMHO it makes no sense to include stuff here that is part of libnDPI.