Why remote desktop fails when you need it most
RDP, Parsec, Sunshine, RustDesk and similar tools all run inside Windows. They need the OS to be booted, the network stack to be up and, usually, a user session to be signed in. Rice-Jones lists a failed update, a BitLocker problem or anything else that blocks the desktop as situations where those tools can't help.
An IP KVM works at a different layer. It is a small network device that does three things:
- Video: it captures the PC's display output over HDMI.
- Input: it sends keyboard and mouse input over USB.
- Network: it presents all of that through a browser or app.
To the PC, the box looks like a monitor plus a keyboard and mouse. Nothing is installed on the host. That is why it can show firmware setup screens, boot menus, recovery screens and a stuck "Restarting…" spinner.
The hardware and wiring
Rice-Jones says this capability used to belong to servers, which have IPMI, or to a few specialised motherboards. He spent weeks hunting for a PCIe IPMI card for the Asus board in his server, and that card works with only a handful of Asus boards. PiKVM, the open-source project, is what brought the idea to ordinary PCs. Current options include JetKVM, NanoKVM and GL.iNet, and all of his current devices are from GL.iNet.
His wiring is simple:
- Connect the PC's HDMI output to the KVM's HDMI input. Integrated graphics can serve as the source.
- Connect one USB cable from the PC to the KVM.
- Connect the KVM to the network. His unit supports PoE, but he powers it from a USB-C wall adapter so it can sit on any switch.
GL.iNet's own documentation for the Comet PoE describes the same layout: Ethernet to the switch, HDMI from the controlled machine into the KVM, and a USB cable to the controlled machine's USB port.
Resolution and refresh rate
Rice-Jones says capture tops out at 1080p60 or 4K30, depending on the device. GL.iNet's app page advertises video quality of up to 4K at 30 fps. Those are device-specific figures, not limits of the whole category, so check your exact model before buying.
If your main monitor is high-refresh, as his is, he suggests giving the KVM a second GPU output. The feed only has to be good enough for maintenance.
Power: the KVM cannot press the power button
Keyboard and mouse emulation does not turn a dead PC on. Rice-Jones describes several workarounds:
- Wake-on-LAN: this wakes a sleeping PC, and the GL.iNet app lists it as a feature.
- A Fingerbot: a small actuator that physically presses the button.
- An ATX control board: it splices into the motherboard's front-panel headers. This is the method that does the job most of the time for him.
- A smart plug plus the BIOS "restore on AC power" setting: this is his fallback. He cycles the plug from Home Assistant. He admits it isn't perfect, and cutting power is not a graceful shutdown.
These options are not interchangeable. Wake-on-LAN needs the PC and network configured to support it. Don't assume a KVM alone can recover a fully powered-off machine.
Getting to it from anywhere: Tailscale
Rice-Jones joined the GL.iNet KVM to his tailnet. He says that means nothing is exposed and no ports are forwarded. GL.iNet's documentation for the Comet PoE confirms the model-specific procedure:
- In the KVM's console, open Apps Center, then Tailscale.
- Enable it and bind the KVM to your Tailscale account.
- Put the controlling device on the same account.
- Browse to the KVM's Tailscale virtual IP. No GLKVM app is needed.
The same docs list ZeroTier, NetBird, the GLKVM app and a vendor cloud service as alternatives. Rice-Jones uses the cloud relay (GoodCloud) only from machines he doesn't want to add to his tailnet, such as a PC he doesn't own. He regards the KVM's availability as dependable: it has no power button, never sleeps and sits behind a whole-house UPS. He adds that if the KVM itself is offline, he has bigger problems than remote access.
What it feels like
He says the BIOS session felt as smooth as sitting at the desk, and he used it to overclock remotely. He reports slight lag in typing and the cursor, comparable to a cloud text editor. For long sessions he still prefers RustDesk, which he finds sharper and smoother. In his setup, the KVM is for rescue and short tasks.
The security caveat
This is the part to read carefully. An IP KVM gives whoever controls it keyboard, video and mouse access at firmware level. That can bypass protections that only run inside Windows, such as endpoint security tools and lock screens.
Eclypsium published research on March 17, 2026. Researchers Reynaldo Vasquez Garcia and Paul Asadoorian found 9 vulnerabilities across 4 KVM vendors, spanning 7 distinct vulnerability classes. The affected products were the GL.iNet Comet RM-1, Angeet/Yeeso ES3 KVM, Sipeed NanoKVM and JetKVM. The flaws covered missing brute-force protection and weak firmware verification, among others.
Patch status varies by vendor:
- Angeet/Yeeso ES3: it carries the worst flaws, including a CVSS 9.8 missing-authentication issue (CVE-2026-32297). Eclypsium's table lists no fix available for the ES3.
- GL.iNet Comet RM-1: Eclypsium's table, as updated, lists the UART root access and brute-force protection issues as fixed in v1.8.2. At launch, The Hacker News reported the brute-force fix in 1.8.1 BETA, with fixes for the firmware-verification and UART issues still being planned. Check the current firmware notes for your exact model.
- JetKVM: version 0.5.4, released March 9, 2026, adds login rate limiting and signed releases.
As of an October 2026 update, none of the nine is in CISA's Known Exploited Vulnerabilities catalog. That is reassuring but not a clean bill of health.
Rice-Jones also mentions the NanoKVM's onboard microphone. He says it is worrying, but that an attacker would already need root access to the device to use it.
Don't treat "private network" as "locked down"
Rice-Jones uses ACLs to limit which devices can reach the KVM. That is the right instinct, but the defaults matter. Tailscale's documentation says a new tailnet's default policy file allows communication between all devices. It also says that with no acls section, Tailscale applies a default allow-all policy. The same page says Tailscale now recommends grants for new policy configurations, while ACLs will continue to work indefinitely.
Being on the tailnet is therefore not least privilege. You have to scope access to the KVM yourself and check what the policy actually allows.
A practical checklist
- Update the firmware before the KVM touches a workstation you care about, and keep updating it.
- Keep the management interface off the public internet. Use a private overlay such as Tailscale, ZeroTier or NetBird, or a dedicated management VLAN. Eclypsium's mitigations, as summarised by Intrucept, include enforcing MFA where supported, isolating KVM devices on a management VLAN, restricting internet access and keeping firmware current.
- Write explicit access rules so only your admin device or devices can reach the KVM, then test them.
- Turn on two-factor authentication if the device offers it. GL.iNet's app lists 2FA as a feature.
- Use cloud relays sparingly. Rice-Jones keeps GoodCloud for occasional use from devices he can't put on the tailnet. The reporting here doesn't establish the relay's full security properties, so don't treat it as a blanket recommendation.
- Plan the power-on path (ATX board, smart plug, WoL) before you need it.
- Know your Windows recovery basics. A KVM lets you reach the BitLocker recovery screen, but you still need the recovery key.
Bottom line
Rice-Jones's conclusion is sound. A KVM-over-IP box complements remote desktop software and doesn't replace it. It restores access when Windows is rebooting, stuck before login or needs a BIOS visit. It is a poor fit for all-day work and won't switch on every PC by itself. It also depends on its own power and network.
The XDA piece gives the Comet X at $280 for a four-device model. That price is the author's reference, and I haven't verified it independently. Cheaper devices exist, but the Eclypsium findings suggest the vendor's update and security practices matter more than the sticker price. A device that can control your PC below Windows deserves the same scrutiny as any other privileged management hardware.
References
- KVM-over-IP gave me an office workstation that actually works from anywhere XDA · 2026-11-16T22:00:21+00:00
- Manage permissions using ACLs · Tailscale Docs tailscale.com
- Your KVM is the Weak Link: How $30 Devices Can Own Your Entire Network - Eclypsium eclypsium.com