Is there a roundabout way to have the Soho mk3 redirect all NTP traffic and send it to a local server? Much like it can intercept DNS queries and force them to the local server?
Reason is that I have my own NTP server that I have my windows and linux servers pointing to, as well as any other devices that use NTP (switches, battery backup, etc) to sync time.
But it is getting tedious having to parse my DNS logs (I’m diverting DNS traffic to a local instance of Deadwood) trying to figure out all the different public NTP servers that my various IoT/Smarthome devices, game consoles, desktops, tablets and mobile phones are using.
Vendors of embedded devices intended for consumer use and even commercial use often hardcode NTP servers into their configs and there is no way to edit them. For example many of my smarthome devices were set by the vendor to use pool.ntp.org or time.nist.gov. Interestingly enough, one of the products seems to want to use NTP servers based in China (probably the dev’s who wrote the code never circled back to localize the NTP settings before hitting the market).
I have read guides that it should be possible to do this with port forwarding, but it seems that the port forwarding config in the Pepwave only let you forward ports inbound from internal to intranet.
Could we either have a capability that would allow us to redirect ports on the lan to another host? And if not, could we have a similar option where the Pepwave would detect and redirect all NTP traffic to the same IP (similar to how it can do for DNS)?
This would be immensely helpful.
PS- I did search the forum for NTP related topics but it seems those discussions revolved around having the device host NTP, rather than have it redirect it.