Project

General

Profile

Actions
Copy link

Feature #15211

open

tcpdump run with BIOS hardware clock set, but no on environment system time

Added by Sergei Shablovsky 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Packet Capture
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

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
Copy link
 #1

Updated by Steve Wheeler 3 months ago

  • Tracker changed from Bug to Feature
  • Priority changed from High to Normal
  • Affected Version deleted (2.7.x)
  • Affected Architecture deleted (All)

This should be an option when running the pcap.

Actions
Copy link
 #2

Updated by Sergei Shablovsky 3 months ago

Steve Wheeler wrote in #note-1:

This should be an option when running the pcap.

Please argue.

All FreeBSD - working in TZ time
All pfSense system - working in TZ time
All pfSense logs (except pcap) - writes in TZ time.
All SysAdmin work in pfSense machine - are INSIDE this both systems.

WHY pcap in pfSense need to use GMT by default???

Ok, just make BY DEFAULT

[x] Write dump events in TZ time (local time in pfSense)

Actions
Copy link

Also available in: Atom PDF