| Summary: | KDE Connect 1.35.2 can't see other devices on same Wi-Fi | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Steffen W. <steffen-winkler> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | andrew.g.r.holmes |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Attached is the KDE Connect log | ||
Hi,
In version 1.35 we added a change that makes KDE Connect only communicate in private networks (site local or link local IP addresses). This means your devices' IP addresses should belong to 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 (assuming IPv4).
Looking at the logs ("Discarding UDP packet from a non-local IP") and the IP range you shared, this seems to be the problem. Why do you use a public IP range for your local network? Unless you are intentionally using internet-routable IPs, this seems a bad setup on your side.
As a workaround, you can download version 1.34.4 from F-Droid but if you have the Google Play version installed you will need to uninstall & reinstall the app: https://f-droid.org/en/packages/org.kde.kdeconnect_tp/
Albert
Could you explain why that change was made? As for why I use that IP range: It's the default IP range of the DHCP server that runs on my router. Further more, that is not some 'special' router, it's an AVM Fritz!Box, one of the most popular router brands in Germany. (In reply to Steffen W. from comment #2) > Could you explain why that change was made? > > As for why I use that IP range: It's the default IP range of the DHCP > server that runs on my router. Further more, that is not some 'special' > router, it's an AVM Fritz!Box, one of the most popular router brands in > Germany. whoops, my bad. I must've changed it at some point. Default is 192.189. not sure why I changed it to what it is now. While I still wonder why the change was made originally, I guess I should thank you for getting my IP range 'in spec' so to speak. KDE Connect 1.35.2 works now. |
Created attachment 189583 [details] Attached is the KDE Connect log After updating KDE Connect on my phone to 1.35.2 I'm now unable to connect to my PCs. In fact, KDE Connect won't even show a PC as available. Even specifying the actual IP address doesn't make it work. I've checked bug report #515707 but I do not have a VPN installed on my phone. STEPS TO REPRODUCE 1. Have a working KDE Connect setup 2. Update KDE Connect on your phone to 1.35.2 from 1.34.4 OBSERVED RESULT KDE Connect is no longer able to connect to any PC EXPECTED RESULT KDE Connect should be able to connect to my computers just like before. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.2 Kernel Version: 6.18.8-arch2-1 (64-bit) Additional information: Since this became relevant in the other bug report, my local IP range is 189.168.187.*