| Summary: | SFTP: Error while try to manage files from computer on mobile | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Roman Akhmadullin <freeman.aka.ahmed> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aleixpol, andrew.g.r.holmes, e.duisters1, sinkapeter, Uhrak.ServIT |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Android | ||
| OS: | Android 7.x | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
syslog
log with key tape problem |
||
|
Description
Roman Akhmadullin
2016-07-16 03:14:02 UTC
Created attachment 100302 [details]
syslog
The IP-adress of phone is wrong, if I change it , and run the sshfs command in terminal, the phone mounts.
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 after update to 1.1 I also cannot connect to mobile filesystem. ( opensuse leap 42.3 and 15.0 ) /var/log/message contains some hint, but I'm not able anything to repair problem. I dont know what to do. Messages says there are no matching key type. How to set up right key type ? Or this is not problem ? Created attachment 116530 [details]
log with key tape problem
log with key tape problem
Fixed by commit 25b86c6c7f9f73c7186244612786edf120cf4860 |