On Sun, Dec 13, 2020 at 7:33 PM Alexander Bluhm <[email protected]> wrote:
> On Sun, Dec 13, 2020 at 06:59:18PM -0300, K R wrote: > > Just found a bare metal i386 P4 machine with the same problem: > > Interresting. Also works with my Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz > > root@ot1:.../~# tcpdump -c 1 -nl -tt -i pflog0 > tcpdump: WARNING: snaplen raised from 116 to 160 > tcpdump: listening on pflog0, link-type PFLOG > 1607898263.001061 10.188.81.22 > 10.188.81.21: icmp: echo request > > How do you generate packets and log? > > I put a "pass log" into my pf.conf and ping the machine from remote. > Can you try that? How does your test setup look like? > Pretty standard: pass log rule, logging traffic from remote machines. > > I use -current. Yours is a 6.8-stable if I recall correctly. > Can you try -current snapshot? > It worked! Just tried -current on both machines, bare metal and under qemu: OpenBSD 6.8-current (GENERIC) #539: Mon Dec 14 03:13:47 MST 2020 server# tcpdump -c 1 -nl -tt -i pflog0 tcpdump: WARNING: snaplen raised from 116 to 160 tcpdump: listening on pflog0, link-type PFLOG 1607982786.117611 146.59.149.107.62566 > xxx.xxx.xxx.xxx.5060: udp 715 server# date -r 1607982786 Mon Dec 14 21:53:06 GMT 2020 server# date Mon Dec 14 21:54:22 GMT 2020 > > On both of your machines' tcpdump time is about time 16 years in > the future. What happens if you use the other -ttt -tttt -ttttt > options? > With -current they all show the correct time. --Kor > > bluhm >
