Comet sending a lot of DNS requests

(Updated gramar :smiley: )

Hello, I came here specifically because of the issue with stun.l.google.com, which I understand is used for WebRTC H.264. However, I don’t use WebRTC, and I would really appreciate the ability to stop the KVM from querying this server so I don’t have to block it manually.

I do not allow any Google-related services or tracking on my local network — not even for WebRTC DNS resolution. It would be considerate to stop resolving this server when WebRTC is disabled, or at least provide an option to change the STUN server (without needing to override it manually via terminal). Forcing Google services on users without consent is a serious security concern for me. Thank you.

Edit:
I would much prefer an official option to disable this behavior, rather than having to manually disable the kvmd-janus service (1) via terminal.

This service checks my external IP via STUN to prepare for NAT traversal — even though I’m not using WebRTC. That’s absurd, and for me, a major security concern. I do not share my real IP with anyone unless I explicitly choose to.

Edit 2 (i did some digging):
Despite disabling the kvmd-janus service and confirming no active Python processes, outbound DNS queries to stun.l.google.com continued to appear in dns logs. Investigation revealed that Janus-related configuration files were still present under /etc/kvmd/janus/, specifically referencing a WebSocket transport socket (janus.transport.websockets.jcfg). This suggests that Janus components remain partially integrated into the PiKVM stack, potentially invoked indirectly by kvmd or other system-level triggers. Will need to investigate this, but looks like even when janus is not running, some remnants are still trying to resolve STUN server (1). If this behavior is not patched, I’ll be forced to manually edit the stack or isolate Comet from the local subnet — which introduces more complexity than the device is meant to solve. In that case, I’ll likely switch to a different solution that aligns with my security standards and does not violate EU directives concerning DNS sovereignty and user consent.