Having unit be an NTP time server would be helpful

[JGordon]

Thanks for the quick response @Eddy_Yeung . I figured it was along shot that there would have been PPS from the GPS receiver feeding into the board running the NTP server.

[collinscochran]

I’ve been seeing not great performance on the NTP server built in. Off by almost a full second. I’ve got it pointed at another NTP server which works within .005s, where if i point NTPd at the pepwave It is off by almost .9s

[Jonathan_Pitts]

@collinscochran What is the time source. See this post:

Having unit be an NTP time server would be helpful

It would be great if 6181 [NTP Server] Added support for NTP Server was added to the Surf SOHO MK3. For security purposes, there are a number of local devices for which I block all WAN traffic (outbound and inbound), but a nuisance is that every time one of those devices gets rebooted, the time on the device has to be manually reset. It would be great if all NTP traffic could be redirected to an internal NTP server on the SOHO. … I understand that the SOHO MK3 probably doesn’t have the RTC chip…

If GPS make sure it has a good view of the sky.

[collinscochran]

I’m using other NTP servers as the time source. Tried the peplink pool as well as apple time, NIST, etc. for some reason we have one device that won’t look beyond the subnet for NTP regardless of how it is configured so this is the workaround, we’d otherwise point it straight at a NTP server.