Support offline JetKVM devices #346

New issue

Open

opened 2026-02-20 08:22:07 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 08:22:07 -05:00

Owner

Originally created by @hertg on GitHub (Jun 25, 2025).

Note

I am creating this as a meta issue, to track the progress of JetKVM becoming usable and user-friendly in offline settings. Please don't hesitate to close this, if you (the maintainers) don't like having meta issues in your repository.

Some people may prefer their KVM devices to have limited or no access to the internet. From a security perspective, with the level of access the KVM device may grant to internal infrastructure, it makes sense to a) not connect it to a cloud service and b) even completely isolate the device from the outside world.

Right now, JetKVM is usable without WAN access, but there's still things that need to be addressed, I am listing them below.

#516 and #534
Timesync does not work because JetKVM uses static public NTP servers; which also leads to HTTPS-mode not working because the self-signed certificates are issued for timespans in the past
#96
It is currently very complex to do app and firmware updates offline
#368
Not necessarily about WAN access, but it should be possible to set a static IP in environments where there is no, or an unstable DHCP server

Maybe there's something I missed, but those are the things I stumbled over while configuring my offline JetKVM devices, please feel free to add to he list.

Originally created by @hertg on GitHub (Jun 25, 2025). > [!NOTE] > I am creating this as a meta issue, to track the progress of JetKVM becoming usable and user-friendly in offline settings. Please don't hesitate to close this, if you (the maintainers) don't like having meta issues in your repository. Some people may prefer their KVM devices to have limited or no access to the internet. From a security perspective, with the level of access the KVM device may grant to internal infrastructure, it makes sense to a) not connect it to a cloud service and b) even completely isolate the device from the outside world. Right now, JetKVM is _usable_ without WAN access, but there's still things that need to be addressed, I am listing them below. - [ ] #516 and #534 Timesync does not work because JetKVM uses static public NTP servers; which also leads to HTTPS-mode not working because the self-signed certificates are issued for timespans in the past - [ ] #96 It is currently **very** complex to do app and firmware updates offline - [x] #368 Not necessarily about WAN access, but it should be possible to set a static IP in environments where there is no, or an unstable DHCP server Maybe there's something I missed, but those are the things I stumbled over while configuring my offline JetKVM devices, please feel free to add to he list.