On Sun, 9 May 2010 15:29:18 +0100 "Martin A. Brooks" martin@hinterlands.org allegedly wrote:

You might have better luck using a regular VPN such as OpenVPN. Here's a HOWTO:

http://hinterlands.org/wiki/index.php/OpenVPNQuickstart

Martin/Brett

Thanks - but unless I'm missing something obvious, the VPN solution won't work easily in my scenario. Bear in mind that I want 90% (or so) of my web browsing to go out normally (unproxied). I only want my tor traffic (from separately configured browsers on various clients) to go via the proxy to the external VPS. And I want a simple configuration which means I point to a local proxy.

If I set up a VPN from my local proxy (say 192.168.1.20) to my VPS (say 195.195.195.195) that will give me a route to the VPS which is independent of the normal default route to the outside. That would mean that I would need to reconfigure my clients to add a new static route to the VPS via the tunnel on the local proxy. That adds a complication I don't want.

Of course, if I could set up a VPN from my external router that would make it slightly easier, but I'm pretty sure my cisco wont run openvpn.

So autossh looks like the way to go (thanks Brett). But I'd still like to know why the tunnel dies.

Mick ---------------------------------------------------------------------

The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?

Douglas E Comer - Internetworking with TCP/IP Volume 1

http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------