Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: tunnelling through 2 servers

Subject: Re: tunnelling through 2 servers
Date: Thu, 21 Dec 2006 00:15:03 -0500
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@TechDude.Ca
m. 416 .414 .9934

http://TechDude.Ca/


From: bforbes <b.forbes2@ugrad.unimelb.edu.au>
Date: Fri, 15 Dec 2006 18:35:23 -0800 (PST)
To: <secureshell@securityfocus.com>
Subject: Re: tunnelling through 2 servers
Resent-From: <secureshell-return-9162@securityfocus.com>
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.



<Prev in Thread] Current Thread [Next in Thread>