Actions
Bug #15211
closedtcpdump run with BIOS hardware clock set, but no on environment system time
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Packet Capture
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:
Description
Brilliant pfSense Stuff!
Please fix :
tcpdump could be run with TZ (Time Zone) set in the whole system environment.
Description and how to replicate :
have wrong timestamp in “ Packet Capture Output” (pcap auto scroll view, the “Diagnostic / Packet Capture” main menu) : exactly 2 hours back shift from system time.
How to fix this?
P.S.
pfSense 2.7.2-RELEASE on bare metal server, System time are correct, timestamps in ALL other logs (syslogd) are correct, NTP are correct, no any NTP servers specified in DHCP per interface, and a reboot not help… ;)
Wrong timestamp in Packet Capture Output
https://forum.netgate.com/topic/185772/wrong-timestamp-in-packet-capture-output
Actions