Hi,
just got my Comets Q and X so I took the X for a spin and quickly found a few things, I’d like to see fixed or as little additional features in a future firmware version and was wondering, why it wasn’t already in it.
-
Network needs IPv6 support, please. We need Hardware IPv6 aware and manageable and not more excuses for people to not use IPv6 because “my device XY doesn’t even support it”
-
as the Comet Pro I also own has the possibility to use Netbird alongside Tailscale, I wanted to ask if Netbird support is also coming to the Comet X (and the Q perhaps?), too. Especially as the X with rackmount and 4-device command console would be a prime target for making it available via Netbird, too. Especially I hope it could get the ability to not only run the Netbird cloud but custom deployments as well (e.g. changeable management URL). Also the product page ( Comet X (GL-RM4PE) Quad-Port Remote KVM with PoE — GL.iNet ) shows all three already (Zerotier, Netbird, Tailscale), so I was wondering why it wasn’t included out of the box.
-
The Cloud management toggle I found only on the touch display settings on the box itself. The webUI and App don’t show any configuration for the cloud mgmt (toggle on/off) nor the option for a self-hosted management variant. If I remember correctly the Comet Pro had the ability to either use gl.inets own service or to self-host your own dashboard for all your comet devices. That was a big point why I backed the Comet Q and X, too, so I could have all of them connected to my own self-hosted dashboard.
-
I found the ability to upload a custom certificate but was wondering, if there would be a way to implement acme.sh or another LetsEncrypt/ACME provider to issue certificates. With certificate runtime going down to 90 days in the future, non-self-issued certificates will be a hassle to change and as the Comet X is more of an infrastructure product as KVM for multiple hosts, it would simply be sensible to make it able to request certificates via ACME and DNS-01 for example
-
Only being able to select the timezones as “UMT+X” was a bit strange, as there’s no toggle for daylight saving time, it would be far easier to just make Timezones like MEST/MST or Europe/ available to remedy that (as just an example) instead having to change the device from UMT+2 to UMT+1 for my timezone.
-
Small’ish thing but would play into the ACME thing as well: You can set up the hostname, but the rest ist “automatically” .local. Using .local is BAD, as it’s a reserved domain for mDNS, Apple automagic stuff and other BS, that has to reason to run in a management network
So please either use .home.arpa or .internal as default (.internal is ratified and an agreed upon TLD to NOT ever be sold and public available so is exactly what people may think .local is while it isn’t!). Also please let me simply change the domain and use the FQDN for the certificate stuff from 4) You could also enable people to simply create a self-signed cert that way with their own FQDN name that matches their infrastructure/management network (e.g. mine is mgmt..tld so my Comet X is kvm01.mgmt..tld). That would be a really nice addition to the simple “certificate management” you have now. -
Bug: the “default” device certificate is only valid from 1970 to 1979. So the certificate is not only invalid in terms of host name (of course) but also in terms of validity. At least make it from 2025/2026 to 2035/2036, that would be usable - so a stricter browser my block the certificate not only because of the wrong name but also because its lifetime is factually over:
- that one is more a question: If one enables the “Virtual Media” “Mount to Remote” toggle, the USB gets mounted to the device and you can copy stuff on it. Would it be possible that if you access the KVM via the app (or the browser but that one would probably be harder?) that you can also access the KVM that way? Or at least have a “file browser” there without all files being simply listed in the UI but more like an actual file explorer with subfolders? That way one could also deploy smaller/little apps or file structures to the target KVM or use it to copy off logs from the device.
- a kinda feature request: would it perhaps be possible to switch a port from “keyboard/mouse+HDMI” to “serial console” mode with using the USB-A 2.0 Port with a compatbile USB2serial cable to manage a switch or network device with the Comet X? Or add the option as a “virtual” 5th port for the front USB-A 2.0 Port? THAT would be incredible to have the ability to not only switch through 3-4 servers but also have the option to enable serial input on a USB Port (on the back or the front) and have that be put on screen so one can also access a switch, firewall, router etc. - that would bring amazing additional possibilities for the device.
Besides those points, the initial feeling while testing the Comet X was quite enjoyable and a great product for bigger homelabs but also for companies with multiple servers. Especially the initial setup handling gets a chefs kiss. Asking for a PIN for the display first and the same in the UX so there’s no default PWs anywhere and the user has to set them up initially is great. Soo often do we have customer setups that run with default credentials for decades - it’s a security nightmare.
So thanks for the nice hardware and I’m hoping a few of these things will make it in over time
Cheers
\jens
