consider me one of the lucky 10000 . Used ssh for years, didn't know this!
SSH Secret Menu
161–170 of 184 posts
Re: SSH Secret Menu
#162consider me one of the lucky 10000 . Used ssh for years, didn't know this! https://xkcd.com/1053/
`ssh -D 1234` to open up SOCKS in the server. This is also flew over my head. I think the gzip one is the most surprising tbh.
Re: SSH Secret Menu
#163I intended to post in defense of manpages. I love manpages. I think most open-source manpages are high-quality, and a few are really outstanding. "It's easier to ask an AI" can be true without implying that manpages are bad. However, "man" the tool does have issues, and one of them bit me just now. So, I didn't know about openssh client escapes like ~?. I thought, "surely that's in the manpage?" I opened the manpage…
Thanks for the suggestions. Invoking man with "-E ascii" fixed this for me. It sounds like some distributions do have this fixed in their default settings. I'm on Cygwin 3.6.6; maybe it's mostly a Cygwin thing.
Cygwin is nice, but it's a Frankenstein's monster. I'd hold back critical thoughts and feelings, until testing elsewhere.
You'll be happiest.
Re: SSH Secret Menu
#164I intended to post in defense of manpages. I love manpages. I think most open-source manpages are high-quality, and a few are really outstanding. "It's easier to ask an AI" can be true without implying that manpages are bad. However, "man" the tool does have issues, and one of them bit me just now. So, I didn't know about openssh client escapes like ~?. I thought, "surely that's in the manpage?" I opened the manpage…
Works for me on Debian (with the default pager, less ).
There was more, then less, but once upon a time there was 'most'.
I miss most.
Re: SSH Secret Menu
#165Earlier quoted context omitted.
The temporary address doesn't stay active while there's a connection on it? I think that would be the actual "fix".
I think it does, but that's not the issue: if the interface goes down all the temporary address are gone for good, not just "expired".
If you're on a stable address, and the interface goes down, will it let your connection/socket continue to exist?
Because if the connection/socket gets lost either way, I don't really care if the IP changes too.
Re: SSH Secret Menu
#166Earlier quoted context omitted.
If hung SSH connections are common it's likely due to CGNAT which use aggressively low TCP timeouts. e.g. I've found all UK mobile carriers set their TCP timeout as low as 5 minutes. The "default" is supposed to be 2 hours, you could literally sleep your computer, zero packets, and an SSH connection would continue to work an hour later, and generally speaking this is still true unless CGNAT is in the way. If you are…
> you could literally sleep your computer, Depends on whether your sockets survive that, though. Especially on Wi-Fi, many implementations will reset your interface when sleeping, and sockets usually don't survive that. Even if they do, if the remote side has heartbeats/keepalive enabled (at the TCP or SSH level), your connection might be torn down from the server side.
Yes, by generally I really mean all the defaults are pretty permissive, but I understand some people tune both TCP and SSH on their servers to drop connections faster because they are worried about resource exhaustion.
But if you throw up a default Linux install for your SSH box and have a not-horrible wifi router with a not-horrible internet provider then IME you can sleep your machine and keep an SSH connection alive for quite some time... I appreciate that might be too many "not-horrible" requirements for the real world today though.
Re: SSH Secret Menu
#167consider me one of the lucky 10000 . Used ssh for years, didn't know this! https://xkcd.com/1053/
`ssh -D 1234` to open up SOCKS in the server. This is also flew over my head. I think the gzip one is the most surprising tbh.
I use that one a lot! It is extremely useful for accessing web-interfaces on switches and firewalls and other devices on a remote network.
Re: SSH Secret Menu
#168This might be a good place to mention: https://linux.die.net/man/1/autossh
Re: SSH Secret Menu
#169Earlier quoted context omitted.
I think it does, but that's not the issue: if the interface goes down all the temporary address are gone for good, not just "expired".
If you're on a stable address, and the interface goes down, will it let your connection/socket continue to exist? Because if the connection/socket gets lost either way, I don't really care if the IP changes too.
I'm not sure what happens to the socket, maybe it's closed and reopened, but with this patch I have SSH sessions lasting for days with no issues. Without it, even roaming between two access points can break the session.