GUI support for ntpd RRD Graphs?
-
It works here.
-
Working here too, only thing I may have done that you didn't mention is a reboot.
-
Could be a browser issue?
-
browser cache cleared; no change.
reboot; fixed it. -
Reboot of PC or pfsense?
-
I think it took about 10 minutes before I saw anything, but hours is a bit extreme.
-
I turned this on yesterday because of this thread, and it popped in right away.. Within a few minutes was seeing datapoints on the graph.. Took a look see this morning and graphs look correct to me. No reboot of anything required.
-
Yeah - Same here. No strange behavior (other than my crappy 10 year old system clock being deviant)
-
What GPS are you using if you dont mind me asking? I am looking to do GPS on my box, and have been searching the threads here. Lots of debate :(
-
On my box I'm not using GPS - Its a short distance to NIST level 1 servers, so I'm synced to 1 Navy and 2 NIST level 1 time servers.
My box is in a crappy location for me to hook up GPS directly. -
I'm looking at a Raspberry Pi with a GPS backpack, under $100 and I can stick a couple other little things on the Pi at the same time. Gives me an excuse to grab one of the new Pi 2s for my other uses.
I'd be interested in other's choices of hardware for a GPS time-base too. See some discussion here:
https://forum.pfsense.org/index.php?topic=87983.msg485108#msg485108
-
"give me an excuse"
Get it… I will use it.
-
Someday I want to run a public NTP server, but not until I get some GPS sources.
I did notice that PFSense is staying quite stable with time, typically within less than 1/2 a millisecond.
Status Server Ref ID Stratum Type When Poll Reach Delay Offset Jitter Candidate 69.162.170.4 200.98.196.212 2 u 416 512 377 35.354 -0.784 1.254 Candidate 69.162.170.5 200.98.196.212 2 u 297 512 377 35.736 0.126 0.333 Outlier 208.100.4.52 199.249.223.123 2 u 408 512 377 14.017 0.353 0.402 Outlier 67.202.100.50 216.218.254.202 2 u 391 512 377 13.498 0.249 0.501 Active Peer 208.100.0.228 164.244.221.197 2 u 52 512 377 13.848 0.379 0.361 Outlier 208.100.4.54 43.77.130.254 2 u 439 512 377 13.832 1.435 0.223 -
This is the one thing on my system that sucks to high heaven. The clock jitter might be half a second or so for mine. Quite terrible.
-
What GPS are you using if you dont mind me asking? I am looking to do GPS on my box, and have been searching the threads here. Lots of debate :(
I've had good luck using Garmin GPS 18x LVC, Adafruit Ultimate GPS breakout v3, and the 'Sure GPS' evaluation board. .
The garmin needs some soldering to power it via USB and the DB-9 connector and won't drive more than 1 PC (in my experience, and not usually a problem). The Adafruit is similar in power and DB-9 soldering needs. The "sure gps", if it's still available on ebay, can be powered by USB but needs soldering on the board to bring the PPS signal to the DB-9 connector.
You definitely need PPS for a serial GPS to be accurate. Without it, the GPS source is worse than your internet-connected servers/peers, so what's the point….
Unfortunately AFAIK all the reasonably priced GPS units need some soldering to get PPS to ntpd. All of this is well documented on the 'net, but unfortunately soldering is a barrier to entry for some folks.
[Edit: update garmin model to 18x LVC]
-
I to would not mind being a stratum 1 time server to the public ;) But if you want to run one run one - pool ntp is really easy to join, my n40l box that runs esxi, pfsense as vm, etc. etc.. Next time I reboot it and ipv6 is enabled on it again will bring up ntp on ipv6 for the pool
But stays pretty stable.
-
This is the one thing on my system that sucks to high heaven. The clock jitter might be half a second or so for mine. Quite terrible.
I see a strong correlation between changing load and offset and skew. It seems the more my system transitions clock speeds, the more it skews. If the system is constantly idle or constantly under load, it's fine, but when network traffic is constantly changing, that's when you see those spikes.
-
The issue posted by OP is actually a bug. https://redmine.pfsense.org/issues/4434
-
I enabled it once, so it must be a very intermittent bug…
