https://bugs.kde.org/show_bug.cgi?id=459171
Bug ID: 459171
Summary: Network discovery is performed only using main
interface (no devices when VPN or multiple interfaces
are connected)
Product: kdeconnect
Version: unspecified
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: windows-application
Assignee: piyushaggarwal...@gmail.com
Reporter: valdi...@gmail.com
Target Milestone: ---
SUMMARY
When I use both Ethernet and Wi-Fi on my laptop (to different networks), or
connect to any VPN using OpenVPN client, KDE Connect could not discover any
devices on the LAN and could not connect to already paired ones.
STEPS TO REPRODUCE
1. Connect to Ethernet and Wi-Fi, make sure KDE Connect devices are only on
Wi-Fi
2. Open KDE Connect, refresh the device list
OBSERVED RESULT
No devices found. Already paired ones, which are present on Wi-Fi network, are
not connected.
EXPECTED RESULT
Devices are discovered and connected.
SOFTWARE/OS VERSIONS
Windows: Windows 10 21H2
Windows KDE Connect "offline installer" build
kdeconnect-kde-21.12.3-903-windows-msvc2019_64-cl
ADDITIONAL INFORMATION
"Faster" network interface types (Wi-Fi vs Gigabit Ethernet), with "Automatic
Metric" feature of Windows (enabled by default), always have lower interface
metric even if it does not install any routes (Windows adds 224.0.0.0/4 for
multicast and 255.255.255.255/32 for broadcast automatically).
Turns out KDE Connect daemon fails to send UDP broadcast packet using all
available interfaces and tries to send it only via default interface (the one
with lowest metric, because it has lower metric route for 255.255.255.255
broadcast address), despite having the code to do so:
https://invent.kde.org/network/kdeconnect-kde/-/blob/a918ffc0cbd7d85a2a482cfa1019508720498517/core/backends/lan/lanlinkprovider.cpp#L164
--
You are receiving this mail because:
You are watching all bug changes.
