[CoLoCo] ssh but kind of a mac question so please forgive

Jim Hutchinson jim at ubuntu-rocks.org
Thu Sep 25 17:23:37 BST 2008


On Wed, Sep 24, 2008 at 7:00 PM, Kevin Fries <kfries at cctus.com> wrote:

> Jim,
>
> SSH is just port forwarding.  It has no concept of protocols.  In short,
> it's just a dumb translator.
>
> If you want other ports forwarded, forward them.
>
> I have never used the notation you are, instead I use the forward local
> notation, and I don't have a reference in front of me... So please translate
> this to what you want.  But if I was trying to ssh tunnel 80 and 443 I would
> enter something like:
>
> ssh -L 80:localhost:5151
>      -L 443:localhost:5152
>      <user at example.com>user at example.com
>
> All on one line of course.
>

Kevin,

Thanks for the info. Here is what I tired. Because my ssh listens on port
5151 I have to use the -p option. Not sure if that means I need to change
the part after localhost or not. I used sudo because it says I have to for
use of privileged ports.

sudo ssh -i /path/to/key -p 5151 -L 80:localhost:5151 user at remote.host

It didn't work. By which I mean that it made the ssh connection just fine,
but traffic on port 80 is not tunneled (I tested by going to a "what's my
ip" site and it's not my home ip as it is when tunneled). Of course, I'm
assuming that if I open a browser and go to www.google.com that it will be
sent over port 80 from the computer. Do I have any guarantee that this
happens? Maybe there is something wrong with the ssh syntax or maybe I need
to use a different port other than the ssh connection port for the
localhost:5151 part.

Any thoughts? Thanks.

-- 
Jim (Ubuntu geek extraordinaire)
----
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-co/attachments/20080925/ee756745/attachment.htm 


More information about the Ubuntu-us-co mailing list