In message <[EMAIL PROTECTED]>, Jason Wood writes:
>Hi All,
>
>I have the following situation and am very new to ssh:
>
> laptop --> boxA -|firewall|-> boxB
>
>The laptops are running a client application that needs to connect to boxB
>(just moved to the firewall).
>
>We have SSH1 running as a server (sshd) on boxB and just as a client on boxA
>(no sshd).
>
>I have tested tunneling via:
> ssh -g -f -L 12345:boxB:23 boxB sleep 100000
> then from my laptop: telnet boxA 12345
>This works fine.
>
>The problem is that the client application requires 201 (literally) ports to b
>e
>open and we also have a development boxC behind the firewall that they will
>need to access the same way.
>
>If there a better way than starting 402 ssh connections on boxA?
You don't say what version you're running, but...
In ssh 1.2.27, you can forward many ports per connection. (I'm sure
that is true for other versions, too.) However, there's a limit of
100. You can either change that value and recompile, or set up ~5
connections.
And for sanity's sake, put the connection setup requests in your config
file...
--Steve Bellovin
