https://bugs.kde.org/show_bug.cgi?id=344432
--- Comment #4 from Sunhoo <sun...@posteo.net> --- I found the sshfs command used by the kdeconnect daemon to try to mount the device: sshfs kdeconnect@10.20.10.10:/ /home/jean/.config/kdeconnect/9a8b63987a327f12/kdeconnect_sftp/9a8b63987a327f12 -p 1739 -f -F /dev/null -o IdentityFile=/home/jean/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin Except that 10.20.10.10 is my tun0 address and it should be using 192.168.0.41 which is my local network address (from wlan0, which is what I'd use when I manually ssh into my device). So when I execute this command manually, it just hangs for 60 seconds then timeout as expected. But if I change the command to: sshfs kdeconnect@192.168.0.41:/ /home/jean/.config/kdeconnect/9a8b63987a327f12/kdeconnect_sftp/9a8b63987a327f12 -p 1739 -f -F /dev/null -o IdentityFile=/home/jean/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin -d I get: FUSE library version: 2.9.7 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 Warning: Permanently added '[192.168.0.41]:1739' (DSA) to the list of known hosts. Permission denied (password). read: Connection reset by peer It waits for the password from the standard input (see "-o password_stdin"), so I enter something then it does seem to find the device but the connection is denied because of the incorrect password. This is normal since this password should be automatically given by KDE Connect and we are not supposed to type it in. So how come 10.20.10.10 is used instead of 192.168.0.41 (in my case)? As a side note, I do use a VPN on both devices but the result is the same when not connected to them. -- You are receiving this mail because: You are watching all bug changes.
