Quick FAQs about GL.iNet KVM¶

This is a brief Q&A collection for GL.iNet KVM, designed to provide quick answers to some common basic questions.

Basic Information¶

Q1. What devices can GL.iNet KVM control?

A1. GL.iNet KVM can control any device that uses HDMI output and USB input, such as laptops, desktops, Raspberry Pi, mini hosts, etc.

In addition, Comet Q (GL-RMQ1) can control any device whose USB‑C port supports DisplayPort Alt Mode for video output; no HDMI port is required. This includes, but is not limited to, certain iPhones, iPads, Android phones, MacBooks, Mac minis, and most modern Windows laptops. Click here for details.

Q2. Do I need to install any software to use GL.iNet KVM?

A2. No software is required to be installed on the controlled device, and it can be Windows, macOS, ChromeOS, Linux, etc.

As to the controlling device, whether a software needs to be installed on it depends on the way you want to access the KVM.

Nearby Control (for Comet 5G only)

Note: This method is only available on Comet 5G (GL-RM10RC).

Comet 5G features Wi-Fi Nearby Control, enabling quick local management without wired connections. Simply switch the Comet 5G's Wi-Fi network mode to AP mode, and it will generate a unique Wi-Fi SSID. Connect to this SSID to securely access the Comet 5G's console. Click here for details.

Activating the AP mode disconnects the Comet 5G from its upstream Wi-Fi and provides nearby access only (with no internet connectivity).

Local Control (for Comet X only)

Note: This method is only available on Comet X (GL-RM4PE).

Comet X provides an HDMI OUT port and two extra USB ports, ideal for local troubleshooting, configuration and OS installation. Simply connect your monitor, mouse and keyboard for plug-and-play local hardware control. Click here for details.

LAN Access

If you want to access KVM over the same local area network (LAN), no software needs to be installed on the controlling device.

Simply open a browser on the controlling device, enter either the KVM's IP address or glkvm.local in the address bar to access KVM locally.

Click here for details.

Remote Access

GLKVM App

If your controlling device runs Windows, macOS, Android, or iOS, you can install the GLKVM app on it and access your KVM remotely, thus accessing the controlled device.

Click here for details.
Cloud Service

This method is ideal for those who cannot or do not want to install the GLKVM app.

Bind your KVM to the Cloud service, then you can access your KVM remotely by typing glkvm.com into a web browser on your controlling device, thus accessing the controlled device, without installing the GLKVM app.

Click here for details.
Tailscale

This method is suitable for those who cannot or do not want to use the GLKVM app or Cloud service, though it involves more steps.

Bind your KVM and controlling device to the same Tailscale account, then you can access your KVM remotely by typing the KVM's Tailscale virtual IP into a web browser on your controlling device, thus accessing the controlled device.

Click here for details.
ZeroTier

This method is suitable for those who cannot or do not want to use the GLKVM app or Cloud service, though it involves more steps.

Join your KVM and controlling device into the same ZeroTier network, then you can access your KVM remotely by typing the KVM's ZeroTier IP into a web browser on your controlling device, thus accessing the controlled device.

Click here for details.
NetBird

This method is suitable for those who cannot or do not want to use the GLKVM app or Cloud service, though it involves more steps.

NetBird is an open-source zero trust networking platform that lets you build secure private networks for home and business use. As a WireGuard®-based overlay network, NetBird enables secure access to your devices anytime and anywhere.

GL.iNet KVM integrates NetBird, allowing you to bind it to the NetBird virtual network for remote access.

Click here for details.

Q3. How do I access GL.iNet KVM?

A3. Generally, you can access GL.iNet KVM either locally or remotely through different ways:

Besides, some GL.iNet KVM models support Nearby Control or Local Control, allowing you to access them on site without connecting to any other router.

Q4. Do I need to open ports (exposed to WAN) for GL.iNet KVM to achieve remote access?

A4. No. No open ports or even a public IP is needed.

Q5. Does GLKVM app support ChromeOS/Linux?

A5. No. Currently the GLKVM app does not support installation on Chrome or Linux OS.

If your controlling device runs Chrome/Linux OS, the GLKVM app cannot be installed, thus remote access to controlled device via GLKVM app is not supported.

However, you can use Cloud Service, Tailscale, ZeroTier, or NetBird to achieve remote access. See Q3 above for details.

Alternatively, you can access the KVM locally via a web browser. See Q3 above for details.

Q7. Can Comet (GL-RM1) connect to wireless network?

A7. No. Comet (GL-RM1) does not support wireless network connection.

It needs to be connected to a network device (e.g., a router) via an Ethernet cable for Internet access.

If you prefer a KVM that supports Wi-Fi, you may consider the following models:

Power Control¶

Q1. Can a GL.iNet KVM remotely power the target device on and off?

A1. GL.iNet KVM allows you to remotely power the target device on and off via the methods below:

Wake-on-LAN (Built-in software service)
ATX board (Sold separately; does not work with Comet Q.)
FingerBot (Sold separately; does not work with Comet Q.)

Q2. How to use ATX Board for remote power control?

A2. Please refer to ATX Board User Guide.

Features¶

Tip

Below are FAQs for several common features. Please refer to the corresponding user guide for full feature details.

Q1. Do I have to use KVM Cloud Service?

A1. No. The Cloud Service is optional.

If you don't rely on the cloud for remote access, you can use third-party overlay networking tools, such as Tailscale, ZeroTier and NetBird.

Q2. Can I use a single GL.iNet KVM to control multiple devices?

A2. The following GL.iNet KVMs can only control one target device:

Comet (GL-RM1)
Comet PoE (GL-RM1PE)
Comet Pro (GL-RM10)
Comet 5G (GL-RM10RC)
Comet Q (GL-RMQ1)

However, Comet X (GL-RM4PE) can connect to up to four target devices simultaneously, though only one device can be controlled at a time. You can quickly switch between the four connected devices via the physical button on the front panel when on site, or via the remote console when away.

Comet X (GL-RM4PE) features four independent channels on the rear panel; each channel comes with an HDMI port for video signal transmission, a Type-C port for keyboard and mouse signal transmission, and a USB 2.0 port for USB peripherals (e.g., Fingerbot or ATX board).

Q3. What is Wake-on-Lan?

A3. Wake-on-LAN (WOL) is a technology that allows a computer or device to be remotely powered on or awakened from a low-power state over a network. It works by sending a "magic packet" containing the target device's MAC address, which triggers the device to start up. Common uses include remote administration, energy-saving standby configurations, and centralized system management.

Q4. Does GL.iNet KVM support Mouse Jiggle?

A4. Yes. You can enable Mouse Jiggle on the KVM console.

The Mouse Jiggler feature simulates subtle, periodic mouse movements to prevent the computer (i.e., the controlled device) from going to sleep due to prolonged inactivity, such as during remote meetings and server management.

Q5. Does GL.iNet KVM support two-way audio?

A5. Yes. You can enable Speaker and Microphone on the KVM console to achieve two-way audio transmission.

Still have questions? Visit our Community Forum or Contact us.