It is done from the client side, even though it has the word "Server" in it.
I usually set it in my .ssh/config file, but I don't know if Windows has a similar thing, hence my reluctance to be any more specific about that.
But I think you can also do it from the command line, something like:
ssh -o "ServerAliveIntereval=120" piuser@pihost
BTW, PUtty has something similar - you set it in one of the configuration menus.
Finally, a couple of software recommendations - that should make your life easier:
1) On the Windows side, check out "MobaXterm" - which is sort of a super-super-set of PUtty.
2) On the Pi side, check out the programs "screen" and/or "tmux" - which will help with keeping your ssh sessions alive even if you get disconnected. Note that "screen" is the older of the two and has the advantage of being small and comprehensible. "tmux" is much more complicated and powerful. Personally, I use both, in different situations.
I usually set it in my .ssh/config file, but I don't know if Windows has a similar thing, hence my reluctance to be any more specific about that.
But I think you can also do it from the command line, something like:
ssh -o "ServerAliveIntereval=120" piuser@pihost
BTW, PUtty has something similar - you set it in one of the configuration menus.
Finally, a couple of software recommendations - that should make your life easier:
1) On the Windows side, check out "MobaXterm" - which is sort of a super-super-set of PUtty.
2) On the Pi side, check out the programs "screen" and/or "tmux" - which will help with keeping your ssh sessions alive even if you get disconnected. Note that "screen" is the older of the two and has the advantage of being small and comprehensible. "tmux" is much more complicated and powerful. Personally, I use both, in different situations.
Statistics: Posted by BigRedMailbox — Fri May 24, 2024 12:37 am







