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.
13 lines
661 B
Plaintext
13 lines
661 B
Plaintext
Guessed flow protos: 1
|
|
|
|
DPI Packets (TCP): 30 (30.00 pkts/flow)
|
|
Confidence Unknown : 1 (flows)
|
|
Num dissector calls: 410 (410.00 diss/flow)
|
|
|
|
Unknown 30 37313 1
|
|
|
|
|
|
|
|
Undetected flows:
|
|
1 TCP 10.10.10.1:1445 <-> 192.168.0.1:20979 [proto: 0/Unknown][ClearText][Confidence: Unknown][27 pkts/35276 bytes <-> 3 pkts/2037 bytes][Goodput ratio: 96/92][6.40 sec][bytes ratio: 0.891 (Upload)][IAT c2s/s2c min/avg/max/stddev: 0/3 267/2832 5666/5662 1131/2830][Pkt Len c2s/s2c min/avg/max/stddev: 66/186 1307/679 1454/1454 393/555][PLAIN TEXT (countrycode)][Plen Bins: 3,0,0,0,3,0,0,0,0,0,3,0,0,0,0,3,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3,0,0,0,0,0,0,0,0,82,0,0,0,0]
|