A thing you can do to get more stable ssh connections on your side is to run a nat service on the machine. For example, running connections on a OS X machine that has parallels installed (virtualization software) and that runs NAT is far more stable than a machine without.
Ask HN: moving beyond screen to persist SSH sessions?
31–36 of 36 posts
I think it might be the change of ip adress that is killing your connectivity. I can close the lid of my macbook running os x or linux, let it fall to sleep, go down to the porch outside and let the machine wake up from sleep and still have the ssh connection active.
Re: Ask HN: moving beyond screen to persist SSH sessions?
#32A VNC or RDP session running on a stable host somewhere, running full screen on your laptop, so you only have one thing to reconnect to. What you want would be cool but it can't be done with TCP/IP.
vnc all the time... if you hate yourself
Re: Ask HN: moving beyond screen to persist SSH sessions?
#33A VNC or RDP session running on a stable host somewhere, running full screen on your laptop, so you only have one thing to reconnect to. What you want would be cool but it can't be done with TCP/IP.
Look in to NoMachine NX (http://nomachine.com/) rather than VNC. For some tasks I use a NoMachine NX desktop on a Linode Ubuntu server from the other side of the planet - it's quite useable. Over 3G web browsing is often faster via the remote desktop than browsing sites directly.
Re: Ask HN: moving beyond screen to persist SSH sessions?
#34The completely unrealistic way to solve this problem would be with Mobile IP:
http://en.wikipedia.org/wiki/Mobile_IP
But I don't know if that has ever really been used outside of a research context.
Re: Ask HN: moving beyond screen to persist SSH sessions?
#35Several people have mentioned running ssh in a loop. Here is an example of that:
http://www.commandlinefu.com/commands/view/357/ssh-tunnel-wi...
Re: Ask HN: moving beyond screen to persist SSH sessions?
#36I have this exact same problem. I don't forward traffic through SSH but I run a service that has almost 30 servers. Sometimes I have connections open to 10+ of them, sometimes (shudder) all of them. When my connection dies I want to throw my computer out the window.
I haven't read the comments here yet but hopefully someone will have at least a partial solution to save my sanity :)