Add option to configure NTP server(s) used by JetKVM device #285

New issue

Open

opened 2026-02-20 08:21:44 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 08:21:44 -05:00

Owner

Originally created by @solemnwarning on GitHub (May 23, 2025).

Originally assigned to: @ym on GitHub.

Some networks have local NTP servers which may be preferred or mandatory. There is also a DHCP option for NTP servers which the device could use, although support for this in general isn't widespread.

Originally created by @solemnwarning on GitHub (May 23, 2025). Originally assigned to: @ym on GitHub. Some networks have local NTP servers which may be preferred or mandatory. There is also a DHCP option for NTP servers which the device could use, although support for this in general isn't widespread.

deekerman added the

component: timesync

label

2026-02-20 08:21:44 -05:00

deekerman commented

2026-02-20 08:21:45 -05:00

Author

Owner

@hertg commented on GitHub (Jun 25, 2025):

I need this for JetKVM to work without internet access. When I go to network settings in the JetKVM GUI, I see that it correctly received my local NTP-Server configuration through DHCP. But looking at the packets (123/udp), JetKVM doesn't seem to consider it -- it tries to reach out to a bunch of external NTP servers.

Without this feature, HTTPS-mode won't work, because the self-signed certificates are issued for a timespan in the past. Also see #534

@hertg commented on GitHub (Jun 25, 2025): I need this for JetKVM to work without internet access. When I go to network settings in the JetKVM GUI, I see that it correctly received my local NTP-Server configuration through DHCP. But looking at the packets (123/udp), JetKVM doesn't seem to consider it -- it tries to reach out to a bunch of external NTP servers. Without this feature, HTTPS-mode won't work, because the self-signed certificates are issued for a timespan in the past. Also see #534

deekerman commented

2026-02-20 08:21:45 -05:00

Author

Owner

@hertg commented on GitHub (Jun 25, 2025):

Just saw that this may get resolved in #625 and/or #609

@hertg commented on GitHub (Jun 25, 2025): Just saw that this may get resolved in #625 and/or #609

deekerman commented

2026-02-20 08:21:45 -05:00

Author

Owner

@hertg commented on GitHub (Jun 25, 2025):

My current workaround is to reroute all 123/udp requests coming from JetKVM to my local ntp server, on MikroTik this can be done with:

/ip firewall nat add action=dst-nat chain=dstnat comment="jetkvm ntp redirect to local" dst-port=123 protocol=udp src-address=<JETKVM-IP>/32 to-addresses=<LOCAL-NTP-IP> to-ports=123

@hertg commented on GitHub (Jun 25, 2025): My current workaround is to reroute all 123/udp requests coming from JetKVM to my local ntp server, on MikroTik this can be done with: ``` /ip firewall nat add action=dst-nat chain=dstnat comment="jetkvm ntp redirect to local" dst-port=123 protocol=udp src-address=<JETKVM-IP>/32 to-addresses=<LOCAL-NTP-IP> to-ports=123 ```

deekerman commented

2026-02-20 08:21:45 -05:00

Author

Owner

@solemnwarning commented on GitHub (Jun 30, 2025):

I recompiled the firmware image with a modified server list, but obvs. that means I've disabled auto-update for the time being.

@solemnwarning commented on GitHub (Jun 30, 2025): I recompiled the firmware image with a modified server list, but obvs. that means I've disabled auto-update for the time being.

deekerman commented

2026-02-20 08:21:45 -05:00

Author

Owner

@snax44 commented on GitHub (Dec 30, 2025):

Any news about this ?
The choice of Google, Cloudflare, and other big tech companies as NTP is debatable, but okay, let's admit it.
However, the fact that the server advised by DHCP is ignored is really, really unfortunate.
This makes JetKVM incompatible with most minimally advanced corporate and residential networks.

That said, I still think JetKVM is the best IP KVM on the market. Thank you for that.

@snax44 commented on GitHub (Dec 30, 2025): Any news about this ? The choice of Google, Cloudflare, and other big tech companies as NTP is debatable, but okay, let's admit it. However, the fact that the server advised by DHCP is ignored is really, really unfortunate. This makes JetKVM incompatible with most minimally advanced corporate and residential networks. That said, I still think JetKVM is the best IP KVM on the market. Thank you for that.