I would like to suggest an optional firmware feature for the Comet 5G / GL-RM10RC that I believe could significantly expand its usefulness without changing the philosophy of the standard product.
First, I want to say that I respect GL.iNet’s decision not to include general-purpose router functionality in the stock firmware. In fact, I think that is a very intelligent design choice.
For an unattended remote KVM, reliability and simplicity are extremely important. Keeping the standard firmware focused on remote-access and KVM functionality reduces complexity, limits additional failure modes, and helps ensure that the device remains available when it is needed most.
I would not suggest changing that.
Instead, I would propose offering a separate, optional firmware image for users who specifically want the Comet 5G to perform two functions simultaneously:
1. Continue operating as an independent 5G-connected remote KVM / out-of-band management device.
2. Provide its 5G connection as an emergency WAN connection to an external firewall or router.
The second function could be implemented through the existing USB-A host port using a supported USB-to-Ethernet adapter rather than changing the role of the Comet’s built-in Ethernet interface.
Conceptually:
5G / LTE
↓
Comet 5G
├── Remote KVM / out-of-band management
└── NAT / IP forwarding
↓
USB-A Ethernet adapter
↓
External router/firewall WAN3
This would allow the built-in Ethernet interface and normal Comet network behaviour to remain unchanged.
GL.iNet could certify a small number of inexpensive USB Ethernet adapters using common ASIX chipsets such as AX88772 and AX88179/AX88179B and include the appropriate drivers in the alternate firmware.
Users wanting this capability would therefore have to make two deliberate choices:
- Download and install the alternate “router-enabled” firmware rather than receiving this functionality in the standard firmware.
- Purchase and connect a supported USB-to-Ethernet adapter.
That creates a very clear separation between the normal supported KVM product and the more advanced dual-purpose configuration.
The use case is particularly compelling for remote offices.
For example, an office might normally have two primary Internet connections connected to its firewall. The Comet 5G could remain completely independent for emergency remote KVM access while also providing its cellular connection to WAN3 on that firewall.
If the primary WAN connections failed, the office would still have limited Internet connectivity through the Comet.
If the firewall itself failed, was misconfigured, or became inaccessible, the Comet would still provide an independent remote KVM path over the same cellular service.
That means one cellular subscription could provide both:
Emergency WAN connectivity + true out-of-band remote management.
From my perspective, this capability would materially change the business case for the product.
I am already interested in purchasing a Comet 5G for this exact purpose. If an officially supported optional firmware image provided this dual functionality, my company would potentially be looking at deploying approximately 30–40 units across our remote offices.
I believe the current stock-firmware design should remain exactly as it is. I am simply asking GL.iNet to consider giving advanced and enterprise users an optional firmware path that unlocks routing/NAT through a supported USB Ethernet adapter.
The hardware appears uniquely well suited to this use case, and it would make the Comet 5G considerably more valuable as an enterprise remote-site resilience device.
Thanks,
David P. Howard of DC
Inovalon Cybersecurity Architect & Developer