2.0.3 logs and gateway RTT

eskild

Hi and thanks for a new pfSense MR.

After upgrading, I have noticed two things that have negatively changed between 2.0.2 and 2.0.3:

In the logs, the time is logged in GMT, not local time. In the dashboard, System Information, the local time/date is shown correctly.
The RTT calculation towards the gateways, is way off. Before the upgrade, avg RTT used to be at ~8ms. After the upgrade, it is reported to be 95ms. Ping from the FW towards the gateway reveals RTT 2.753ms:

PING xxx.xxx.212.1 (xxx.xxx.212.1) from xxx.xxx.213.187: 56 data bytes
64 bytes from xxx.xxx.212.1: icmp_seq=0 ttl=255 time=2.810 ms
64 bytes from xxx.xxx.212.1: icmp_seq=1 ttl=255 time=2.481 ms
64 bytes from xxx.xxx.212.1: icmp_seq=2 ttl=255 time=2.497 ms
64 bytes from xxx.xxx.212.1: icmp_seq=3 ttl=255 time=3.003 ms
64 bytes from xxx.xxx.212.1: icmp_seq=4 ttl=255 time=2.648 ms
64 bytes from xxx.xxx.212.1: icmp_seq=5 ttl=255 time=3.024 ms
64 bytes from xxx.xxx.212.1: icmp_seq=6 ttl=255 time=3.327 ms
64 bytes from xxx.xxx.212.1: icmp_seq=7 ttl=255 time=3.069 ms
64 bytes from xxx.xxx.212.1: icmp_seq=8 ttl=255 time=2.140 ms
64 bytes from xxx.xxx.212.1: icmp_seq=9 ttl=255 time=2.529 ms

–- xxx.xxx.212.1 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.140/2.753/3.327/0.338 ms

Attaching a snapshot from the RDD graphs that shows the before/after upgrade differences.

Thanks,
//Eskild
pfSense-2.0.3-RTT.png
pfSense-2.0.3-RTT.png_thumb

cmb

You haven't changed your monitor IP to something out on the Internet for instance? I haven't seen any change in gateway monitoring on a number of systems, and upwards of 4000 unique IPs have updated via auto-update alone and doesn't seem like anyone else has seen that.

Also not seeing any logs anywhere being logged in anything other than the correct time of the system. Did you set the timezone after the reboot since upgrade? Certain things won't log with changed timestamps until they're restarted after the timezone is changed.

eskild

I have not changed anything wrt config between 2.0.2 and 2.0.3. The gateway address is my default gateway at the ISP (dhcp over fiber).
I tried a reload just before this post, but I have the same issues after the reload.

I have a 2.1 installation on another fw, and the GMT time log issue is present there as well.

[Edit]
My timezone is Europe/Oslo.

At the shell, date shows GMT:
[2.0.3-RELEASE][root@skfw01.skaarnet.local]/root(1): date
Tue Apr 16 12:31:56 UTC 2013

Thanks,
//Eskild

jasonlitka

I am seeing the same issue with an internal device. My network has two pfSense boxes at the edge of my core network, then another L3 device that separates the core from the clients. both my pfSense boxes are reporting >250ms to travel the 10ft or so to my core router. It seems to be intermittent though as I just refreshed the page a bunch and now it says 1ms.

jimp

I wonder if it might be related to this commit:

https://github.com/pfsense/pfsense-tools/commit/48c04e03d35a984d31a475c427f477f9c511b378

eskild

I could not possibly say but, I'm happy to test in any way I can though.