Hello,
One can also setup an IP to be a type of gateway such as 127.0.0.2 (or even
the servers real IP). Then all traffic to that IP will be forwarded within
the tunnel to the server.
PS: Some older versions Microsoft RDP clients will not connect to any
172.0.0.0/8 address.
Regards,
--
Jason Muskat | GCFA, GCUX - de VE3TSJ
____________________________
TechDude
e.
Jason@...
m. 416 .414 .9934
http://TechDude.Ca/> From: bforbes <
b.forbes2@...>
> Date: Fri, 15 Dec 2006 18:35:23 -0800 (PST)
> To: <
secureshell@...>
> Subject: Re: tunnelling through 2 servers
> Resent-From: <
secureshell-return-9162@...>
> Resent-Date: Wed, 20 Dec 2006 09:28:44 -0700 (MST)
>
>
> I have achieved something that sounds similar to what you want. I have a web
> server at my workplace with a site I'm working on. I can secure shell in
> through the firewall easily enough to edit the site, but I also need to view
> the page in a browser, and the web server is not yet internet-facing. So I
> used ssh to get port 80 traffic through the encrypted tunnel.
>
> Here are the hosts:
> home: my home computer
> firewall: the internet-facing firewall computer
> server: the web-server
>
> ssh -L 2345:server:80 bforbes@firewall
>
> Now in the browser, I go to the url "localhost:2345", and these packets get
> passed through the encrypted tunnel to port 80 on the web-server, problem
> solved.
>
> Hopefully this helps.
>
> --
> View this message in context:
>
http://www.nabble.com/tunnelling-through-2-servers-tf2829801.html#a7902748> Sent from the SSH (Secure Shell) mailing list archive at Nabble.com.
>
