Bug 427310 - device discovery not working in ipv6-only network
Summary: device discovery not working in ipv6-only network
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-03 21:02 UTC by Daniel
Modified: 2021-03-30 22:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2020-10-03 21:02:18 UTC 
SUMMARY
Currently, device discovery seems to only work in an network with ipv4, probably due to the broadcast address used in lanlinkprovider.


STEPS TO REPRODUCE
1. Have a ipv6-only network.
2. Have two kdeconnect-devices.

OBSERVED RESULT
They won't automatically discover each other. Only if you add one using a hostname, it works.

EXPECTED RESULT
Device discovery should also work in an ipv6-only network. I've tested it with multiple devices and am quite sure this isn't a network configuration mistake causing this bug.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.8.13-arch1-1
OS Type: 64-bit
Comment 1 Daniel 2020-10-17 22:02:15 UTC 
The correct IPv6 equivalent of IPv4 broadcast is this multicast address: ff02::1%wlan0, where wlan0 is the interface, of which the local devices should be discovered.
Comment 2 Thiago Macieira 2021-03-30 22:12:45 UTC 
(In reply to Daniel from comment #1)
> The correct IPv6 equivalent of IPv4 broadcast is this multicast address:
> ff02::1%wlan0, where wlan0 is the interface, of which the local devices
> should be discovered.

Do not ever use ff02::1. Get a multicast address for KDE Connect instead.