https://bugs.kde.org/show_bug.cgi?id=337685
Nicholas Killewald <captains...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |captains...@gmail.com
--- Comment #19 from Nicholas Killewald <captains...@gmail.com> ---
I'm getting the same issue with the KDE Connect app 1.6.1 and Android 7.1.2
(using a Pixel). It looks like what's happening is that Android is reporting
the wrong IP address to the KDE side of things (in my case, the
"v4-rmnet_data6" interface, which seems reasonably like "rmnet0" that Sergey
noted in the initial description).
Looking over the source of the Android app, I can see exactly where it happens:
getLocalIpAddress() in SimpleSftpServer.java is going through all the available
network interfaces until it finds the first non-local IPv4 address, or the last
IPv6 address if it never finds an IPv4. On my phone, at least, v4-rmnet_data6
shows up in the list before a "real" address, so when SftpPlugin.java gets the
message to start browsing (in onPackageReceived()), it sends out that IP
address, meaning the KDE side tries to connect to it to no avail.
This appears to be device-specific; on my Nexus 9 (Android 7.1.1), I don't get
any rmnet-related interfaces or IP addresses, and the filesystem browser works
perfectly there. It's only on my Pixel that I get this problem.
That said, I'm not sure how you could definitively tell what the "real"
interface is on the Android device to get the proper IP address, unless the KDE
side instead defaults to using whatever address it just used to send the
message to start browsing.
--
You are receiving this mail because:
You are watching all bug changes.
