 | 1 | initial version |
The hex dump import, like text2pcap can support a timestamp in front of each packet, using the format specified.
There seems to be a bug in Wireshark, in that if no individual packet timestamps are given, then there is no increment of the timestamp between packets, whereas text2pcap does do this.
I'm not sure, but I think neither Wireshark or text2pcap make any adjustments from the time supplied to UTC, the time is copied verbatim, i.e. as the time in a pcapng file is UTC, then the input time is regarded as UTC.
| | 2 | No.2 Revision |
The hex dump import, like text2pcap can support a timestamp in front of each packet, using the format specified.
There seems to be a bug in Wireshark, in that if no individual packet timestamps are given, then there is no increment of the timestamp between packets, whereas text2pcap does do this.This now seems to be OK.
I'm not sure, but I think neither Wireshark or text2pcap make any adjustments from the time supplied to UTC, the time is copied verbatim, i.e. as the time in a pcapng file is UTC, then the input time is regarded as UTC.
