https://bugs.kde.org/show_bug.cgi?id=524876
Bug ID: 524876
Summary: IPv6 addresses in customDevices are never contacted by
LAN discovery
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
DESCRIPTION
On Linux, an IPv6 address can be configured in
~/.config/kdeconnect/config:
[General]
customDevices=2400:....
However, refreshing KDE Connect does not send any packet to that
IPv6 address. tcpdump only observes the normal IPv4 broadcast:
255.255.255.255:1716
No IPv6 packet to the configured custom device is emitted.
STEPS TO REPRODUCE
1. Have two hosts with routable IPv6 connectivity.
2. Verify IPv6 connectivity between them.
3. Add the remote IPv6 address to:
~/.config/kdeconnect/config
[General]
customDevices=<remote IPv6>
4. Restart kdeconnectd.
5. Run:
sudo tcpdump -ni any 'udp portrange 1714-1764 or tcp portrange 1714-1764'
6. Run:
kdeconnect-cli --refresh
OBSERVED RESULT
Only an IPv4 broadcast to 255.255.255.255:1716 is emitted.
No packet is sent to the configured IPv6 custom device.
EXPECTED RESULT
KDE Connect should attempt discovery/connectivity to the explicitly configured
IPv6 address.
ADDITIONAL INFORMATION
IPv6 connectivity itself is confirmed to work:
- The Linux machine can ping the Android device over IPv6.
- A Python HTTP server bound to the Linux machine's global IPv6
address can be reached successfully from the Android device.
Therefore the failure is not caused by lack of routed IPv6
connectivity between the devices.
--
You are receiving this mail because:
You are watching all bug changes.
