tcpdump and timezone mismatch (STABLE 14 vs STABLE 13)

From: mike tancsa <mike_at_sentex.net>
Date: Thu, 14 Sep 2023 16:24:45 UTC 
Just starting to play around with RELENG_14 and noticed one odd thing I 
didnt see in the UPDATING notes.  The server's Timezone is set to EDT 
(GMT-4), but tcpdumping the pflogs show it in UTC.

# date
Thu Sep 14 12:22:11 EDT 2023
# tcpdump -ner /var/log/pflog | tail -1
reading from file /var/log/pflog, link-type PFLOG (OpenBSD pflog file), 
snapshot length 200
16:21:18.848111 rule 0/0(match): block in on vtnet0: 185.11.61.68.52750 
 > xxx.yyy.zzz.141.33428: Flags [S], seq 4237808372, win 1024, length 0

#

Same with dumping pflog0 in real time

# tcpdump -nei pflog0 action block
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on pflog0, link-type PFLOG (OpenBSD pflog file), snapshot 
length 262144 bytes

16:22:59.205362 rule 0/0(match): block in on vtnet0: 198.12.88.139.58870 
 > xxx.yyy.zzz.141.4963: Flags [S], seq 3991681664, win 1024, length 0

Is there a way to change this behavior ? Is it expected ?

     ---Mike