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: Binding ssh to a loopback address

Subject: Re: Binding ssh to a loopback address
Date: Sat, 07 May 2005 15:31:30 +1000
CP Lim wrote:
I was trying to forward a remote port to one at local (but not 127.0.0.1) by doing :

ssh -b 127.0.0.2 -L80:localhost:80 remotehost

That's a local forward, but what you're describing is a remote forward. I'm assuming the command is correct but the description is wrong (since you also said it works w/out the -b.


Anyway, that command will try to bind the client's end of the SSH connection to 127.0.0.2, so what you're trying to do is make an SSH connection from 127.0.0.2 to your remotehost. Sending the connection out 127.0.0.2 won't go anywhere (hence the "no route to host" error).

What you need to do is this:

ssh -L 127.0.0.2:80:localhost:80 remotehost

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

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