Your subject line mentions ssh, but I don't see anything in the body about using ssh for its interactive shell mode, only for tunneling. If you use a Linux client and a Linux server, is it also bad? This would determine whether the problem is that the Linux server is always bad, or if there is something particular to how the OSX client behaves that is bad. Last edited by jesnow on Mon 6:47 pm edited 1 time in total Yes I have thought of alternatives to working this way, but I am trying to figure *this* part now and will go down the rdp rabbit hole later.
SLOW SSH SHELL HOW TO
I was thinking it was the finder previews that were holding things up, but I've noticed the directory displays without them, and only loads them later anyway.Īny insights you may have on how to get the whole thing to be more responsive, I would greatly appreciate. I can use zoom with no delay at all, even with ssh, in the terminal the directory listing is instantaneous. The gentoo server (Core i7 16GB) has 1gbps up and down, My ping to where I am now is around 60ms, which I think is about as good as it gets, and d/l speed from the client 200mb/s, up only 5mb/s but still we dreamed about such transfer speeds back in the day. Files transfer in both just fine, but directories take for-effing-ever to load. *** Here's the problem: It's slow as mud! Like 30 seconds to get the initial directory listing. Helps if you set up passwordless for the ssh login, it will still ask you for your samba password. So you do something like ssh -L 127.0.0.1:44445::445 and you can mount the samba share in and off you go. But they don't give an error message, they open but they don't work. The new wrinkle is that medium ports between 1024 and (I think) 8192 don't work either. No listening on low ports for user in Catalina, period. The workaround with a 127.0.0.2 loopback alias didn't work either, that's new. Same thing with reverse-tunneling samba - you can't use privileged ports like 445 as user, even if you're not using them "Operation not permitted", well we knew this.
SLOW SSH SHELL MAC
The Mac won't let you use /Volumes as user. Sshfs works but you have to remember to put the mount point in user-controlled space. That offered some problems, but also works.
SLOW SSH SHELL PRO
On the inside I'm running samba and it works quite well locally, with the usual complaints and workarounds.Ĭoming in from outside I am using a macbook pro with new catalina. There is just a pinhole to the outside on a nonstandard port, and I listen on ssh for incoming connections. I have my gentoo boxes behind a firewall, as they should be. Posted: Sun 1:08 pm Post subject: Remote file access *slow*: smb, ssh, sshfs Gentoo Forums Forum Index Networking & Security Remote file access *slow*: smb, ssh, sshfs So instead of typing ssh -C -p 1022 -i ~/.Gentoo Forums :: View topic - Remote file access *slow*: smb, ssh, sshfs You can add a bunch of usefull options so that you don't have to type them each time: User So you can type ssh lin + Tab and it should autocomplete to ssh linux-srv. One cool advantage is that now ssh will provide autocomplete for this server. Make sure the IP address match your server IP. You can do so on a per host basis if required :) example: Host linux-srv (Note: you would have to create the directory $HOME/.ssh if it does not exist) You need to edit your "user ssh_config" file which is: vi $HOME/.ssh/config In case you don't have root access (sudo), you can still configure it. This is just a complement of the answer of Book Of Zeus.
0 kommentar(er)
