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.
10 lines
635 B
Plaintext
10 lines
635 B
Plaintext
Guessed flow protos: 1
|
|
|
|
DPI Packets (TCP): 26 (26.00 pkts/flow)
|
|
Confidence Match by port : 1 (flows)
|
|
Num dissector calls: 414 (414.00 diss/flow)
|
|
|
|
TLS 26 12163 1
|
|
|
|
1 TCP 188.75.184.20:49542 <-> 251.182.120.32:443 [proto: 91/TLS][Encrypted][Confidence: Match by port][cat: Web/5][13 pkts/9962 bytes <-> 13 pkts/2201 bytes][Goodput ratio: 93/67][84.45 sec][bytes ratio: 0.638 (Upload)][IAT c2s/s2c min/avg/max/stddev: 186/186 7406/5844 21467/15787 7157/5701][Pkt Len c2s/s2c min/avg/max/stddev: 56/56 766/169 1328/189 433/46][Plen Bins: 0,0,0,0,51,0,0,0,0,9,4,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,4,0,9,9,0,0,0,4,0,0,4,0,4,0,0,0,0,0,0,0,0]
|