nDPId/schema
Toni Uhlig 613bfa91dc bump libnDPI to 85a8ed8a10c033b5e18822608b34e0ce9536f0a5
Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
2025-12-09 10:38:15 +01:00
..
daemon_event_schema.json bump libnDPI to 85a8ed8a10c033b5e18822608b34e0ce9536f0a5 2025-12-09 10:38:15 +01: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 e9751cec26d80fe2d88706d4f7521a63ec12b3bb 2025-10-29 13:51:07 +01: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.