https://bugs.kde.org/show_bug.cgi?id=507954
Bug ID: 507954
Summary: mDNS reply is not bound to the network interface the
request came from
Classification: Applications
Product: kdeconnect
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
kde connect daemon sends MDNS response using incorrect interface on multi-homed
network.
The response packet is not bound to the same interface from where the request
came from, which forces the response to the well-known 224.0.0.251 MDNS IP
address to go via the routing table and the default route (which may be another
interface).
STEPS TO REPRODUCE
1. Connect to two network interfaces, only one of which has default route
(eth0), and another one is its IP range only (LAN-only, eth1)
2. Connect another device (Android smartphone) to the second (LAN-only)
network
3. Press "refresh" on another device
OBSERVED RESULT
The mDNS request comes from Android device via LAN-only interface (eth1), but
the mDNS reply goes via default route (eth0).
The device is not found upon refresh.
EXPECTED RESULT
The device is found upon refresh. mDNS reply goes via the same network
interface.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.8.3
Kernel Version: 6.15.8-100.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
