nDPI
nDPI copied to clipboard
ntop
Open Source Deep Packet Inspection Software Toolkit
## Describe the bug Because ndpi_patchIPv6Address will replace all :0: to ::, the results may have ip like this 2600:1901::16a9:: . It's a wrong ipv6 format, it has multiple '::'
## Describe the bug Questioning how goodput ratio is calculated when pcap includes retransmissions. ### Expected behavior I would expect goodput is simply the cumulative non-zero payload packet size sent...
It might be useful to have some kind of packet dissection and flow management provided directly from nDPI itself. Not sure of the extension of this topic: some "basic" code...
p0f/Satori like signature from TCP syn packets ...
I am using DNS server on a custom port 1234. nDPI fails to recognize the packets as DNS due to hardcoded port 53 in detection. I've found [this](https://github.com/ntop/nDPI/issues/725) issue, but...
## Describe the bug Looks like this change of adding ndpi_str to the function call ndpi_domain_classify_size is breaking while we are tyring to execute in the DEBUG_TRACE mode and also...
Does nDPI has any plan in the roadmap to support WSP/WTP protocol? Reference: [WSP](https://wiki.wireshark.org/Wireless_Session_Protocol) [MMS](https://wiki.wireshark.org/Multimedia_Messaging_Service_Encapsulation) Thanks Subhajit
eDonkey is definitely not as used as >10 years ago, but it seems it is still active. While having a basic TCP support seems easy, identification over UDP doesn't work...
See: https://github.com/ntop/nDPI/commit/8fbef7fb5ab682b7aa9c92e4fd6e106698eb4ae1 https://github.com/ntop/nDPI/commit/9e549ba781a87cb0131c439939e27fd5fd050f10