Displaying 1 result from an estimated 1 matches for "31t16".
Did you mean:
31,16
2018 Jan 27
1
[Bug 1217] New: ULOGD2 JSON Plugin Timestamp Failure
...critical
Priority: P5
Component: ulogd
Assignee: netfilter-buglog at lists.netfilter.org
Reporter: djcanadianjeff at gmail.com
Using ulogd2 on my OPENWRT/LEDE router with the json output plugin in the
ulogd.json file the timestamp shows up wrong "1969-12-31T16:00:00.358281" my
guess is it is trying to use the hardware clock instead of the software clock
that gets updated from NTP.
in the ulogd_syslogemu.log file it shows the correct time "Jan 26 02:45:43"
because its an embedded router device there is no reason for it to have a
hardware...