Fix nBPF matches

Author: IvanNardi

src/lib/ndpi_main.c

@@ -9965,6 +9965,8 @@ static ndpi_protocol ndpi_internal_detection_process_packet(struct ndpi_detectio
 	  ndpi_fill_protocol_category(ndpi_str, flow, &ret);
 	  proto_stack_update(&flow->protocol_stack, ret.proto.master_protocol, ret.proto.app_protocol);
 	  flow->confidence = NDPI_CONFIDENCE_NBPF;
+	  /* Reason: nBPF match */
+	  internal_giveup(ndpi_str, flow, &ret);
 
 	  return(ret);
 	}

tests/cfgs/default/result/h323-overflow.pcap.out

@@ -26,4 +26,4 @@ Acceptable                       1 58            1
 
 Unspecified                      1 58            1            
 
-	1	TCP 192.168.1.1:31337 -> 192.168.1.2:80 [proto: 458/HomeRouter][Stack: HomeRouter][IP: 0/Unknown][ClearText][Confidence: nBPF][FPC: 0/Unknown, Confidence: Unknown][DPI packets: 1][Breed: Acceptable][1 pkts/58 bytes -> 0 pkts/0 bytes][Goodput ratio: 7/0][< 1 sec][Plen Bins: 100,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
+	1	TCP 192.168.1.1:31337 -> 192.168.1.2:80 [proto: 458/HomeRouter][Stack: HomeRouter][IP: 0/Unknown][ClearText][Confidence: nBPF][FPC: 0/Unknown, Confidence: Unknown][DPI packets: 1][Breed: Acceptable][1 pkts/58 bytes -> 0 pkts/0 bytes][Goodput ratio: 7/0][< 1 sec][Risk: ** Unidirectional Traffic **][Risk Score: 10][Risk Info: No server to client traffic][Plen Bins: 100,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]