FW: port forwarding

From: Jesse C. Waters (jwaters_at_triad.rr.com)
Date: 01/20/04

  • Next message: Darren Tucker: "Re: "PAM rejected by account configuration" and "fatal: monitor_read: unsupported request: 24" problem at secong sshd instance" 
    To: <secureshell@securityfocus.com>
Date: Mon, 19 Jan 2004 23:00:43 -0500

    If you can get by without using squid there is ssh -l <user> <remote
    host> -D <non reserved port>
    This is socks 4/5 port forward. Set your browser socks to localhost <non
    reserved port>.
    Get you up and running atleast.

    HTH,

    Jesse

    -----Original Message-----
    From: Dave Markham [mailto:dave.markham@fjserv.net]
    Sent: Monday, January 19, 2004 12:38 PM
    To: Ed J. Aivazian; Payal Rathod
    Cc: secureshell@securityfocus.com
    Subject: Re: port forwarding

    I think you need his ip instead of 127.0.0.1. It has been ages since I
    done this but I have a note of doing it like this :-

    ssh -l <user> -f -N -T -L 2000:<remote machine>:<remote port> <remote
    machine>

    Then connected my browser to localhost:2000

    The -L is your listening port and forwarding it to <remote
    machine>:<remote
    port> , then the remote host to create the tunnel too.

    May be worth a try
    Dave

    ----- Original Message -----
    From: "Ed J. Aivazian" <stealth@arminco.com>
    To: "Payal Rathod" <payal-ssh@staticky.com>
    Cc: <secureshell@securityfocus.com>
    Sent: Friday, January 16, 2004 9:01 AM
    Subject: Re: port forwarding

    > Hello Payal,
    > Looks nice..
    > let's take another matter, are there strong reasons for using squid
    > through ssh tunel? If no, configure your browser to use his proxy
    > server directly. If yes, try telnet-ing to his <ip> 3128. If you still

    > have 'connection refused' there is no daemon to listen tcp 3128.
    > Else, there does not seem to be any other explanation.
    > Note: if you wish ssh to bind to all the interfaces you have on your
    > machine, not only localhost, you should use -g option.
    >
    > Thursday, January 15, 2004, 7:20:08 PM, you wrote:
    >
    > PR> Hi,
    > PR> A friend of mine and me are trying to use port forwarding so that
    > PR> I
    can
    > PR> use his server for browsing the net. He has Mandrake Linux, squid
    > PR> and
    ssh
    > PR> installed. We both are very fresh to ssh.
    > PR> His squid runs on port 3128.
    > >>From my machine I did,
    > PR> ssh -2 -C -l payal -L 1080:127.0.0.1:3128 <ip>
    > PR> and logged to his machine. Then I fired up my browser and pointed
    > PR> the proxy to 127.0.0.1:1080. But when I type any URL I get in the
    > PR> windows where I had ssh running, channel 2: open failed: connect
    > PR> failed: Connection refused
    > PR> channel 2: open failed: connect failed: Connection refused
    > PR> channel 2: open failed: connect failed: Connection refused
    > PR> channel 2: open failed: connect failed: Connection refused
    >
    > PR> What is wrong? I am using Mandrake 9.2. Thanks a lot and eagerly
    waiting
    > PR> for some input on this.
    >
    > PR> With warm regards,
    > PR> -Payal
    >
    >
    >
    >
    >
    >
    > --
    > Best regards,
    > Ed mailto:stealth@arminco.com
    >

  • Next message: Darren Tucker: "Re: "PAM rejected by account configuration" and "fatal: monitor_read: unsupported request: 24" problem at secong sshd instance"

    Relevant Pages