From 9a1c2d0ea731724edfaca97195c87569e4321681 Mon Sep 17 00:00:00 2001 From: Toni Uhlig Date: Thu, 20 May 2021 14:55:05 +0200 Subject: Reworked layer 4 flow length naming/calculation. * nDPIsrvd services usually do not care about layer4 data length, payload length is quite more essential for further processing Signed-off-by: Toni Uhlig --- examples/c-captured/c-captured.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'examples/c-captured/c-captured.c') diff --git a/examples/c-captured/c-captured.c b/examples/c-captured/c-captured.c index 6ffb0296a..1bddd7d52 100644 --- a/examples/c-captured/c-captured.c +++ b/examples/c-captured/c-captured.c @@ -390,8 +390,8 @@ static enum nDPIsrvd_callback_return captured_json_callback(struct nDPIsrvd_sock } nDPIsrvd_ull total_l4_bytes = 0; - perror_ull(TOKEN_VALUE_TO_ULL(TOKEN_GET_SZ(sock, "flow_tot_l4_data_len"), &total_l4_bytes), - "flow_tot_l4_data_len"); + perror_ull(TOKEN_VALUE_TO_ULL(TOKEN_GET_SZ(sock, "flow_tot_l4_payload_len"), &total_l4_bytes), + "flow_tot_l4_payload_len"); if (flow_user->detection_finished != 0 && (total_l4_bytes > 0 || ignore_empty_flows == 0) && -- cgit v1.2.3