Cross Post: SSH server that supports.....

[Need4Speed]

"allowing machines other than the SSH server machine to connect to the forwarded port.) Note that this feature is only available in the SSH 2 protocol, and not all SSH 2 servers support it (OpenSSH 3.0 does not, for example)."

basically, I establish a ssh tunnel from client A to server B across the internet. Server B is a linux box, client A is a windows box. Once the tunnel is setup, I want to connect a third box, client C also a windows box on the same lan as server B, through Server B to client A.

 

[chsh1ca]

With some trickiness with Netcat and ssh you could accomplish this, but why not simply drop in a static route to Server C that uses Server B as the gateway? That way A and C would know how to talk directly, and B would just direct traffic, so to speak, and wouldn't need anything more than simple routing configuration.

 

[Need4Speed]

might you be able to explain that to me in more detail....i know enough to be dangerous about routing, but not enough to help me here.

In detail

Client A is a SSH client (no server), windows behind NAT
Server B is the SSH server, linux behind NAT
Client C is SSH Client (no server), windows behind proxy

I plan on starting a SSH tunnel from C (inside the proxy out) to B . I then want access of that tunnel on Client A through Server B.

 

[Need4Speed]

...can anyone help with this?

 

[chsh1ca]

That's not really doable in any useful direct fashion I can think of just off the top of my head. You need an SSH server on either A or C, and the client on A or C to properly handle what you're asking.

What you CAN accomplish is the following:

{A} ==ENC==>{B}==PTX==>{C}
{A}<==PTX=={B}<==ENC=={C}

Where PTX = Plaintext (ie: not encrypted) and ENC = Encrypted traffic.

 

[Need4Speed]

i got that to work as you show it...

tunnel from:
C--->B

and then
B--->A

I can now connect from A to C

I'd like to establish the tunnel from B--->A automatically, but one of the problems I'm having, is that the SSH server on A can't do public/private key exchange without a password. The SSH server on A is part of RemotelyAnywhere.

 

[Need4Speed]

I got it to work with my orginal configuration ... that is:

C ssh's to B and sets up port forwarding
A then ssh's into B with another tunnel.

B is the only machine with the SSH server.