Timeline for How to reliably keep an SSH tunnel open?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 25, 2019 at 2:32 | history | suggested | Xilexio | CC BY-SA 4.0 |
dead link fix
|
| Jan 25, 2019 at 0:58 | review | Suggested edits | |||
| S Jan 25, 2019 at 2:32 | |||||
| Feb 20, 2014 at 0:14 | comment | added | Lambart | @metamatt, that lower-ranked answer you reference is lower-ranked for good reason: IT IS WRONG. | |
| Jan 26, 2012 at 21:54 | comment | added | metamatt | Thanks, this helped. But note (from a lower-ranked answer here, superuser.com/a/146641/115515) that if you specify ServerAliveInterval and not ServerAliveCountMax, you may find ssh intentionally disconnecting sooner than you wanted. | |
| Dec 2, 2009 at 21:16 | comment | added | Darren Hall | The interval specified is in seconds, so you can provide some fine tuning. If your stateful firewall has a 5 minute idle timeout, then 60 or 120 seconds is enough to keep the connection open. It's one of the ways I keep my ssh sessions through my home router open. | |
| Sep 28, 2009 at 13:47 | history | answered | CesarB | CC BY-SA 2.5 |