This is for 1/3rd of my friends list

[moonwick]

I've done some searching, but it appears that what I want doesn't actually exist.

What I want is essentially a client/server VPN-style program that can be aware of more than one internet connection on the client machine and take advantage of that to facilitate failover without interrupting underlying TCP connectionsHere's the scenario I'm

Comments

[moonwick]

It's mostly a matter of convenience. I normally have a ton of SSH sessions open for work, and it's a pain to have to reconnect all of these if I need to switch from one internet connection to another.

Ideally I'm mostly concerned about failover-- a brief 2-3 second pause is more than alright, since TCP can easily handle that without dropping a connection. That being said, if I can have my pony and eat it too, there's nothing wrong with some load-balancing in there as well. :D

The VPN in question is UDP based, and I've had good luck so far running it through both Sprint and Verizon. FWIW, latency on EVDO rev A is <200ms with a good signal, so it's getting quite a bit better. (rev 0 is more like 500-600ms, it seems.)

[anonymous]

Ahh, things make a little more sense now.

Are these tunnels things you could launch via a script (Even a $variable script), or are they always something that needs to be punched out by hand?

[moonwick]

Yeah, and I might ultimately resort to that. There's a certain geek appeal to the fancy, auto-failover tunnel solution, though... :)

[kd5mdk]

The immediate answer to that is obviously to have one ssh connection to the colo box, and then ssh sessions from there to all your other endpoints. :)

[_fool]

yeah--if you're going to induce a hop through the colo box regardless, just ssh and use screen. you can multiply-attach screen if you want more than one window on the various sessions you have established, and screen's been damn good at resizing apps running inside it (mutt, epic4, vim) for some time now.

i like the elegance of what you're proposing, but i don't think it gains you much if you're just ssh'ing anyway. if you had some connection like a forever-running ftp client or server on your MBP...that might be worth hunting for a solution to.