still happened after running this ?
ethtool -s eth0 speed 100 duplex full autoneg off
I can confirm it is still happening to me after running that command
Try this firmware. I've upgraded ConnMan to version 1.45 to see if it resolves the issue.
Although I think the chance of this firmware solving it is slim, I can't really pinpoint what exactly is causing the problem.
I experienced the error again. I stayed connected to one of my instances over several days and the connection remained stable. However, both the device I was connected to and the other one were showing as "offline" in the GUI.
When analysing the issue via SSH, I found that Tailscale's MagicDNS had overwritten /etc/resolv.conf, pointing DNS to 100.100.100.100 (Tailscale's internal resolver). This resolver couldn't resolve external hostnames, which caused the STUN
server lookup (stun.l.google.com) to fail repeatedly:
Can't get STUN info: gaierror: [Errno -3] Temporary failure in name resolution
Without STUN, WebRTC couldn't establish connections, so the devices appeared offline despite kvmd running normally.
Fix: Either disable MagicDNS on the device (tailscale set --accept-dns=false) or ensure /etc/resolv.conf includes a public DNS fallback (e.g. 8.8.8.8) before Tailscale's 100.100.100.100.
Suggestion for devs: The firmware could either pin a public DNS fallback in resolv.conf, or the STUN lookup could fall back to a hardcoded IP when DNS resolution fails.
We will disable tailscale dns.
1 Like
The best experience I had with this device was returning it for a full refund.
UPDATE for anyone still having this issue. I was able to resolve it by setting a static IP in the settings menu of the KVM itself. Previously I had set a static IP for the KVM on my router, and then had the KVM set to use DHCP.
I’ve kept the static IP reservation on my router, but I simply changed the KVM to also use a static IP, with that being the same IP that I reserved for it on the router. To do this, open the settings menu on the KVM, scroll to the bottom, and in the “Network” section at the very bottom, click on the IP next to the word “Ethernet”. Then choose the “Static” tab instead of DHCP. I filled out all of the fields to the exact same values as they were on the DHCP tab.
This seems to have solved the issue for me.
OK, so this is still the DHCP issue. May I ask what brand and model your router is?
I have a similar issue - newly connected GL-RM1 Comet (firmware V1.8.2 release1) dropped off network after 24hrs which suggests DHCP lease issues. Router is a BT Home Hub. Currently unable to gain access as the machine it is connected to has become unresponsive and unable to gain physical access until the end of the week.
Will report back.
Please configure a static IP address on KVM. We have not yet fully identified what the issue is.
The combination of Current Version: V1.8.2 release1 connman 1.45, with static IP set on my router and on the Comet has fixed the drop out issue. Thanks everyone for all your help.
GL-RM1 Comet (firmware V1.8.2 release1) was flashing white. Happy after power cycling. I’ve given it a static IP - let’s see what the next 24hrs brings.
I have a similar issue with a Comet Pro. After about 24-48 hours the KVM needs to be rebooted in order to get past the bios splash screen. If I reboot it is fine…until another 24-48 hours passes…then a reboot is needed. Should the Comet Pro also be at 100 Mbps? My network controller shows a 1000 Mbps (1 GB) connection.
I don't understand your scenario. What do you mean by "BIOS screen"? Which BIOS screen are you referring to? Is it the HDMI OUT? This case is discussing how the KVM becomes inaccessible after a period of time.
Poor choice of words…not the BIOS at all. If I don’t reboot the KVM every 24-48 hours It gets stuck on the splash screen when I start the PC. If I reboot the KVM first then the screen properly shows the correct GRUB screen where I can choose Windows or Ubuntu.
I’m really looking forward for the fix, but for now I’ll try out a new different kvm product
Does your BIOS not like USB composite devices that include a USB flash drive? Try disabling virtual media?
I really have no clue what you mean…
The Comet GL-RM1 use to work great for me for a couple of months. The experience was flawless. But now it just stopped working. I’m not sure what to do next. I’ll keep coming back to this thread and wait for a fix. I hope that once there is a fix, I can just turn off the Comet and back on and it works, or unplug ethernet and re-plug and it works.