[solved] sshfs not working for me

[tinypoodle]

Mounting the extension, extracting content and then squashing it does work - at least on 2.10

[tinypoodle]

On a side note, I just noticed an error in my submission.

The openssh and openssl-0.9.8h dependencies are not required by sshfs-fuse-2.2 on the client.
 
Could whoever administers the extensions please remove them from the dependency list and info file.

Thanks.

Done.

At current those deps are present, as well in 2.x as in 3.x repos.
And I recall having given up on sshfs-fuse a few months ago already, exactly to avoid those deps, when I preferably use dropbear over openssh.

The openssh deps were removed, but I reinstated them in an updated submission after further testing revealed that while dropbear and sshfs-fuse worked well on the same network, connections to outside hosts would hang and timeout.

I've just tested them together again... without success. If you plan on using dropbear/sshfs-fuse only on a local network, then a possible workaround would be to manually remove openssh from the sshfs-fuse dep file.

However, I'm open to other suggestions.

Works like a charm for me for access over internet with dropbear, no openssh whatsoever.
(For reasons of accuracy, this on TC 2.10 and openssl has been installed already for other purposes.)

Also works fine with dropbear/sshfs client side, and dropbear/sftp server side on LAN.

My suggestion would be to consider to remove openssh from dep file and perhaps a line in .info that if for a user it would not work with one of the other ssh clients, then to try openssh.

[combo3]

Actually, the copy/paste process is no longer necessary.

Server Setup

1) Download and install the extension sftp-server submitted by Daniel Barnes

ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tcz/
ftp://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/tce/

(Note: although these files are located in the TC 1.x respository they work just as well with TC 2.2)

I should probably update that ...

Sounds like a plan  

Code: [Select]

tc@box:~$ tce-load -i /tmp/tce/optional/sftp-server.tcz
mount: mounting /dev/loop4 on /tmp/tcloop/sftp-server failed: Invalid argument
/tmp/tce/optional/sftp-server.tcz: OK
Took me a while to find out that this extension is in a format other than squashfs...  

Ah <<light slowly comes on>> so that's why it stopped working.

I'll check it out later today and see if I can get sshfs-fuse working with dropbear and a repackaged sftp-server.

Thanks for your feedback.

[danielibarnes]

I'll update the sftp-server extension today and get it submitted.

[curaga]

Code: [Select]

tc@box:~$ tce-load -i /tmp/tce/optional/sftp-server.tcz
mount: mounting /dev/loop4 on /tmp/tcloop/sftp-server failed: Invalid argument
/tmp/tce/optional/sftp-server.tcz: OK

Just to confirm, this was on 2.x? This should not happen in later versions (showing OK when mount fails).

[tinypoodle]

Yes, that was under 2.10

But a 'file sftp-server.tcz' would explain everything, different filesystem used in prior version (have deleted that after converting it to squashfs).

[tinypoodle]

I'll update the sftp-server extension today and get it submitted.

Thanks, appreciated  

[combo3]

Well, I spent several hours this weekend trying to get sshfs-fuse to work with dropbear and sftp-server without success.

Maybe it's a problem on the host side (A backup server at work running DSL v3.4.11 with OpenSSH_3.6.1p2 Debian 1:3.6.1p2-9, SSH protocols 1.5/2.0, OpenSSL 0x0090702f)

Incidentally, I noticed there are two extensions in the repository (sshfs-fuse-2.2, and sshfs-fuse), so I tried them both.

Since the latter occupies a smaller footprint, I suppose mine can be removed.