After logging with the app for a long while on multiple days, I've finally got home to analyze the data in detail.
Sadly, I can't correlate the events I've written down to the events recorded in the PCAP, because the timestamp seems to overflow or otherwise get corrupted after around 4000 seconds.
(I've already noticed, that the timestamp in the PCAP are just since the start of recording, but as the recording start time is contained in the file name, I thought that wouldn't be an issue. )
It'd be great if you can fix this issue and also record the actual time stamp when the packet was received to make it easier to analyze the pcaps later.
Otherwise, great app so far. Thanks for your work!
Edit: The highest timestamp I've seen over my 32.000 captured packets was 4294.880189 s, then the following packet was back at 0.692653s. That's suspiciously close to the integer limit for a 32-bit microsecond timestamp (4294.967295).
After logging with the app for a long while on multiple days, I've finally got home to analyze the data in detail.
Sadly, I can't correlate the events I've written down to the events recorded in the PCAP, because the timestamp seems to overflow or otherwise get corrupted after around 4000 seconds.
(I've already noticed, that the timestamp in the PCAP are just since the start of recording, but as the recording start time is contained in the file name, I thought that wouldn't be an issue. )
It'd be great if you can fix this issue and also record the actual time stamp when the packet was received to make it easier to analyze the pcaps later.
Otherwise, great app so far. Thanks for your work!
Edit: The highest timestamp I've seen over my 32.000 captured packets was
4294.880189s, then the following packet was back at0.692653s. That's suspiciously close to the integer limit for a 32-bit microsecond timestamp (4294.967295).