pfsense 2.6.0 Time‑Zone Setting: Resolving Log Timestamp Ambiguity During DST Transitions
19K reputation · 28 Jun 2025, 19:46 UTC
Background
In pfSense 2.6.0 the global time‑zone setting under System > General Setup drives the OS clock and all local timestamps in the web interface and syslog. The NTP client synchronizes the clock, but the zone is applied only after boot; during an NTP adjustment logs may temporarily show UTC‑like timestamps until the zone is reloaded.
Current Ambiguity
When logs are forwarded to an external syslog server, pfSense transmits RFC 5424 timestamps with a local zone offset. RFC 5424 does not enforce a strict offset field, which can lead to ambiguity during daylight‑saving transitions. Documentation states that pfSense does not automatically adjust log timestamps for DST changes, and administrators must manually verify offsets when reviewing older logs.
Unresolved Decision
There is no official patch or documented feature request addressing potential misalignment of log timestamps during DST changes, leaving this behavior unresolved.
Questions
- In pfSense 2.6.0, does the NTP client re‑apply the configured time‑zone after each synchronization, or is the zone only set at boot?
- When forwarding logs to an RFC 5424‑compliant syslog server, how is the local offset represented, and does the server reliably interpret it during DST transitions?
- What configuration or workaround can guarantee that log timestamps remain consistent across DST changes without manual offset verification?
pfsense