https://bugs.kde.org/show_bug.cgi?id=518043
Bug ID: 518043
Summary: KDE Connect should not share it's UDP port with other
users
Classification: Applications
Product: kdeconnect
Version First 25.12.3
Reported In:
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: desktop-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Currently, KDE Connect shares it's UDP port with the kdeconnectd's of all other
kde connect users on the system. This very often breaks discovery, as it is
pretty random on which instance incoming messages are delivered (The kernel
will sort-of round-robin them). The QUdpSocket::ShareAddress option is not
meant to be able to use an occupied port without coordination between its
owners. It's only for applications that actively negotiate/coordinate the usage
between them, kdeconnect is not doing that.
The sharing of the UDP port is probably the cause for my android phone having
lot's of difficulties to connect to my desktop, even though I have added my
desktop's hostname as manual connection in the phone's app.
IMHO, kdeconnect should either choose a free UPD port (like the TCP port) or
completely omit the UDP port. As far as I can see, it is only used for
discovery (and being broken at it, as explained above). Discovery could be left
to protocols designed for it (mDNS), or manual peer IP/port configuration. Both
can directly advertise/use the TCP port.
STEPS TO REPRODUCE
1. Log multiple users on to a single host, with all users using kdeconnect
OBSERVED RESULT
All user's kdeconnectd advertise the same UDP port. For almost none of the
users their phones connect reliably to the desktop.
EXPECTED RESULT
Unique UDP ports and reliable discovery / connections.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux forky/sid
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
