aboutsummaryrefslogtreecommitdiff
path: root/tests/result/Oscar.pcap.out
diff options
context:
space:
mode:
authorIvan Nardi <12729895+IvanNardi@users.noreply.github.com>2022-07-24 17:46:24 +0200
committerGitHub <noreply@github.com>2022-07-24 17:46:24 +0200
commite6b332aa4a1399e33df68998cf8351bccaee3fc4 (patch)
tree3fd8ebf02b0af5334b203055e22e4fe139f0cbf4 /tests/result/Oscar.pcap.out
parent523f22b942b1649272e7b89000d25db6278aa1b0 (diff)
Add support for flow client/server information (#1671)
In a lot of places in ndPI we use *packet* source/dest info (address/port/direction) when we are interested in *flow* client/server info, instead. Add basic logic to autodetect this kind of information. nDPI doesn't perform any "flow management" itself but this task is delegated to the external application. It is then likely that the application might provide more reliable hints about flow client/server direction and about the TCP handshake presence: in that case, these information might be (optionally) passed to the library, disabling the internal "autodetect" logic. These new fields have been used in some LRU caches and in the "guessing" algorithm. It is quite likely that some other code needs to be updated.
Diffstat (limited to 'tests/result/Oscar.pcap.out')
-rw-r--r--tests/result/Oscar.pcap.out2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/result/Oscar.pcap.out b/tests/result/Oscar.pcap.out
index a82f38290..c24351f0b 100644
--- a/tests/result/Oscar.pcap.out
+++ b/tests/result/Oscar.pcap.out
@@ -2,7 +2,7 @@ Guessed flow protos: 1
DPI Packets (TCP): 33 (33.00 pkts/flow)
Confidence Match by port : 1 (flows)
-Num dissector calls: 351 (351.00 diss/flow)
+Num dissector calls: 352 (352.00 diss/flow)
TLS 71 9386 1