[Nottingham] Dealing with a router that does not support Port Forwarding

[Jason Irwin]

On 07/05/15 13:43, Mike Cardwell wrote:
> If you run this from your Pi:
>    ssh -R 12345:127.0.0.1:22 some.other.host

That pretty much did it, although I had to add a few other other flags,
from memory:
    ssh -TfN -p 12345 54321:localhost:22 foo at bar.com &
(No TTY, force to backround & send output to /dev/null and do not
execute a command)

Once I had the ssh server on "bar.com" set to allow "GatewayPorts" it
worked really well. Much better than using Cygwin via a Jitsi call!
Unfortunately the ssh link has died, I am not yet sure what went wrong
as I don't have access.

Other than a crontab entry to (somehow) check for the link every few
minutes and then re-create it if it's missing, is there a better way to
ask the ssh client to keep a link alive?
I've looked through the man page and can't see anything obvious.

There's also a VPN in-play so if SSH normally keeps links alive, then
that could well be screwing things up. Seems OpenVPN isn't keeping the
connection alive like I expect it to (I have "KeepAlive 10 30" in the
config file), so I've had to add a crontab to check that every few
minutes and re-establish the link if it goes down).

This, and other exciting things, all explained (possibly sworn about)
this Thursday!

-- 
╔═════════════╦══════════════════════════════════════════╗
║ Jason Irwin ║ OpenPGP (GPG/PGP) Public Key: 0xD0C592B1 ║
║             ║ Import from hkp://pgp.mit.edu            ║
╚═════════════╩══════════════════════════════════════════╝