diff options
| author | Ivan Nardi <12729895+IvanNardi@users.noreply.github.com> | 2025-01-10 19:22:47 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-10 19:22:47 +0100 |
| commit | d351907af8b93020d5d4ac2949d8e9dd0cfb0dd7 (patch) | |
| tree | e5367055061feab97d6090a0c2baf668bd92d082 /doc/FAQ.md | |
| parent | 89ccc30e9f5adb90332a4cf1fe83eec05bb22f74 (diff) | |
Improve documentation (#2661)
Integrate .md files into official documentation
See: https://stackoverflow.com/questions/46278683/include-my-markdown-readme-into-sphinx/68005314#68005314
Diffstat (limited to 'doc/FAQ.md')
| -rw-r--r-- | doc/FAQ.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/FAQ.md b/doc/FAQ.md index 75e568de6..41efa0843 100644 --- a/doc/FAQ.md +++ b/doc/FAQ.md @@ -1,6 +1,7 @@ + # FAQ -From https://www.ntop.org/ndpi/ndpi-internals-and-frequent-questions/ +From [blog post](https://www.ntop.org/ndpi/ndpi-internals-and-frequent-questions/) **Q**: How nDPI implements protocol detection?\ **A**: nDPI includes a list of protocol dissectors (364 as of today) that are able to dissect protocols such as WhatsApp or TLS. As soon as a new flow is submitted to nDPI, the library applies in sequence dissectors that can potentially match the protocols (i.e. telnet is a TCP-based protocol, and it will not be considered for UDP flows). We start from the dissector that can most probably match using the port number. This means for traffic on TCP/22 nDPI will start with the SSH dissectors and if not matching continue with the others. Dissection completes as soon as a protocol matches or when none of them matched and in this case the flow will be labelled as Unknown. |