https://bugs.kde.org/show_bug.cgi?id=365731
Andy Holmes <andrew.g.r.hol...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrew.g.r.hol...@gmail.com
--- Comment #2 from Andy Holmes <andrew.g.r.hol...@gmail.com> ---
This bug was recently reported by a user of GSConnect[1] where the incorrect IP
address was reported by the Android app. The address reported by the app was in
the Class A range (eg. 10.0.0.0), where the device's real address was in the
more reasonable Class C range (eg. 192.0.0.0).
Probably this is a regression or re-occurance of bug #337685 which was fixed[2]
by ignoring "rmnet" connections. FWIW, the reporter also seems to be using a
Xiaomi device like the user in comment 1.
I'm just going to fix this in GSConnect by pulling the address from the active
TLS connection since I'm unaware of there ever being two different IPs used to
communicate with the same device, and the IP in the packet sent by the app can
just be ignored.
[1]: https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/66
[2]:
https://github.com/KDE/kdeconnect-android/commit/c5022358de3a5c3f6bbde44915ae48702cee719d#diff-c1d48f8ae6c815183fccb4b612c5cefa
--
You are receiving this mail because:
You are watching all bug changes.
