Readme written with an LLM but replaced the em dashes with two dashes. Also the ASCII table is off and incorrect. I fail to care at this point

Hi Ramon, yes i used AI to help with Readme, am not as confident in english as i like to be. and the problem with the ASCII table was because i added "egress" and it messed up the Table, thank you for noticing and thank you for checking out my project.

These kinds of dismissive comments for anything that involves AI are doing our industry a huge disservice. Not everyone is adept at English, not everyone can be bothered to hand write the readme when AI can (and did here) do a perfectly good job.

There's an old idiom about this but I'm really getting tired of people here being against everything AI. It was the same when IDEs came out. Everyone banging on about their emacs setup or whatever, meanwhile the rest of us just got on with doing the things we love with the right tools for the job without any nostalgic dogma getting in the way.

AI is here to stay, you need to get used to it or you'll be left behind.

It helped me not read it, so please do keep it up!

Would love to see a screenshot of the dashboard.

Am planning to test it on a big scale and wanted to add dashboard of it then as a screenshot on git. Thank you for checking out the project.

Looks like it just integrates with Grafana.

> Deep L7 inspection -- Optional TLS SNI and DNS query extraction for domain-level visibility into encrypted traffic.

Nice feature. Would be useful to add active traffic management block/drop in the future, in addition to the existing passive analysis.

Thank you for the advice i always look for Feedback. am Always searching for new ideas.

I kinda built(vibe-coded) the same thing[1] but decided to go full C instead of rust.

[1] https://github.com/NoFear0411/spliff