forked from osmocom/wireshark
Fix conversation table when using epoch based time
Ensure that if using tshark -q -t e -z conv,tcp the reported
start time is relative to the epoch time and not relative to
the time of the first packet in the capture file.
Thanks to Theresa Enghardt for reporting the issue and to
Peter Lei for initialy looking into it.
(cherry picked from commit f099bd179a
)
This commit is contained in:
parent
cb432b878e
commit
489fc40a49
|
@ -58,6 +58,12 @@ iousers_draw(void *arg)
|
|||
printf("%s | Frames Size | | Frames Size | | Frames Size | Start | |\n",
|
||||
display_ports ? " " : "");
|
||||
break;
|
||||
case TS_EPOCH:
|
||||
printf("%s | <- | | -> | | Total | Relative | Duration |\n",
|
||||
display_ports ? " " : "");
|
||||
printf("%s | Frames Bytes | | Frames Bytes | | Frames Bytes | Start | |\n",
|
||||
display_ports ? " " : "");
|
||||
break;
|
||||
case TS_RELATIVE:
|
||||
case TS_NOT_SET:
|
||||
default:
|
||||
|
@ -207,6 +213,9 @@ iousers_draw(void *arg)
|
|||
} else
|
||||
printf("XXXX/XXX XX:XX:XX");
|
||||
break;
|
||||
case TS_EPOCH:
|
||||
printf("%20.9f", nstime_to_sec(&iui->start_abs_time));
|
||||
break;
|
||||
case TS_RELATIVE:
|
||||
case TS_NOT_SET:
|
||||
default:
|
||||
|
|
Loading…
Reference in New Issue