https://bugs.kde.org/show_bug.cgi?id=427310
--- Comment #7 from [email protected] --- I seemed to have figured out the problem. Kdeconnect uses two methods for device discovery: multicast DNS or UDP broadcast Multicast DNS is preferred when available; however, kdeconnect uses the system's mDNS to perform it. UDP broadcast is the fallback but is ipv4 _only_ (the ipv6 protocol doesn't even do broadcast). On Android, mDNS works out-of-the-box, but on Linux systems you need Avahi installed and running (kdeconnect doesn't support mDNS via systemd-resolved, sadly) So if you find yourself on a v6-only network with kdeconnect not functioning, try installing/enabling Avahi -- You are receiving this mail because: You are watching all bug changes.
