https://bugs.kde.org/show_bug.cgi?id=515707
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from [email protected] --- I can confirm this regression is present in v1.35.2 and breaks VPN-based setups (specifically Tailscale). My Setup: * Device: Samsung SM-F9460 * OS: Android 16 * App Version: KDE Connect v1.35.2 * Network: Tailscale (100.x.y.z range) * Method: "Add Device by IP" (Manual entry) Investigation & Logs: * Network Verification: I verified connectivity from the phone using Termux. Running nc -z -v <desktop-tailscale-ip> 1716 succeeds immediately, confirming the tunnel is up and ports are reachable. * The Failure: despite the open network path, the KDE Connect app fails to discover or pair with the device. * Log Evidence: The internal KDE Connect app logs show the following error when the packet arrives: I LanLinkProvider: Discarding UDP packet from a non-local IP Conclusion: It appears v1.35.2 introduced a strict check in LanLinkProvider that discards packets from VPN interfaces (like tun0) because they are not recognized as "local" by the standard connectivity check. This logic seems to override the user's explicit intent when using "Add Device by IP." Workaround: I have confirmed that downgrading to v1.34.3 immediately resolves the issue and allows the connection over Tailscale to succeed. -- You are receiving this mail because: You are watching all bug changes.
