All Apps and Add-ons

Pfsense Event date time wrong

ggudgin
Explorer

For anyone having issues with event time not matching the timestamps from pfsense's syslog. It all starts off OK and at what seems random times the date and time starts jumping around. I believe it is due to IPv6 events being interpreted as date and time.
Adding a props.conf to /opt/splunk/etc/apps/TA-pfsense/local with the following:

[pfsense]
TIME_PREFIX = ^
TIME_FORMAT = %b %d %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 15

This limits splunk to only parsing the first 15 characters of the syslog message from pfsense.

Other notes, although not supported, this worked with TA_pfsense on splunk 6.5 and also manually installed in 7.02 (although the later is not listed as supported.)

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...