Besside-ng 1.5.2 rev 1ebb0417 calculates wrong time stamps

[ZerBea]

besside-ng calculates wrong time stamps (time stamp of BEACON and time stamps of EAPOL frames are the same). That prevent calculation of EAPOL time values.

To reproduce it, run wireshark in parallel with besside-ng.

$ tshark -r wireshark.pcap -T fields -e frame.number -e frame.time
1 Aug 1, 2019 16:50:56.022723000 CEST
2 Aug 1, 2019 16:50:56.106049000 CEST
3 Aug 1, 2019 16:50:56.108995000 CEST

$ tshark -r besside-ng.cap -T fields -e frame.number -e frame.time
1 Aug 1, 2019 16:50:56.109057000 CEST
2 Aug 1, 2019 16:50:56.109057000 CEST
3 Aug 1, 2019 16:50:56.109057000 CEST

Attached both cap files
example.zip

BTW:
besside-ng running into the same handshake detection issue as mentioned here:
#1993
and there are a many gcc 9.1.0 warnings when compiling the whole suite.

[ZerBea]

The same applies to latest git head wpaclean.
Steps to reproduce:
Download example cap file from here:
https://wiki.wireshark.org/SampleCaptures?action=AttachFile&do=get&target=wpa-Induction.pcap
Run wpaclean:
$ ./wpaclean test.cap wpa-Induction.pcap
Pwning wpa-Induction.pcap (1/1 100%)
Net 00:0c:41:82:b2:55 Coherer
Done
Verifiy timestamps of test.cap by tshark:
$ tshark -r test.cap -T fields -e frame.number -e frame.time
1 Jan 4, 2007 07:14:51.510267000 CET
2 Jan 4, 2007 07:14:51.509261000 CET
3 Jan 4, 2007 07:14:51.510267000 CET

BEACON == same time as M2

BTW:
Congratulation for release of 1.6., but there are still many gcc 9.2.0 warnings during compiling.