Network Packet Parser with a PostgreSQL Connection.
Go to file
gurkenhabicht a324836a90 made osi Layer 3+4 optional, table layout will be dynamic 2020-05-19 18:28:32 +02:00
src made osi Layer 3+4 optional, table layout will be dynamic 2020-05-19 18:28:32 +02:00
.gitignore further init 2020-05-13 00:04:54 +02:00
Cargo.lock further init 2020-05-13 00:04:54 +02:00
Cargo.toml added rayon to toml file 2020-05-18 16:53:17 +02:00
README.md Update README.md 2020-05-13 16:23:42 +02:00

README.md

This is experimental

This version is a successor of the _POSIX_C_SOURCE 200809L implementation in which all of the data of a parsed pcap/pcapng file is written as a single and simple query. This is done rather fast (tested writes: 100*10^3 tcp packets in ~1.8 sec) but may be insecure.

Postgres databases have a custom maximum limit on each insert query of prepared statements. In order to solve this issue, parsed data is written in chunks. This value is initialized in the config file called parser.json as insert_max.

Currently, ethernet, IPv4 and TCP are the only network protocols handled.