RE: some tunnelling help needed

From: Black, Braden (BBlack_at_VSCat.com)
Date: 02/17/04

  • Next message: Nicholas Nam: "RE: some tunnelling help needed" 
    Date: Tue, 17 Feb 2004 11:42:10 -0500
To: "Payal Rathod" <payal-ssh@staticky.com>, <secureshell@securityfocus.com>

    > -----Original Message-----
    > From: Payal Rathod [mailto:payal-ssh@staticky.com]
    > Sent: Monday, February 16, 2004 12:12 PM
    > To: secureshell@securityfocus.com
    > Subject: some tunnelling help needed
    >
    >
    > Hi,
    > At a friend's place, their ISP suddenly stopped outgoing port
    > 80 traffic
    > due to their misconfigured firewall. I suggested,
    > ssh -2 -C -L 1082:127.0.0.1:3128 <a remote server ip with
    > squid installed>
    >
    > This got one machine on net. But the for rest they would have
    > to do the
    > same. So they tried this on 192.168.10.1,
    > ssh -2 -C -L 1082:192.168.10.1:3128 <a remote server ip with squid>
    >
    > where 192.168.10.1 is their default Linux gateway/proxy (squid).
    >
    > Now I thought that just by changing their proxy port in all windows
    > browsers from 192.168.10.1:3128 to 192.168.10.1:1082 everyone can have
    > net access, but apparently it didn't work out.
    >
    <--SNIP-->

    You forgot the '-g' option, to allow remote hosts to connect to the local
    port. Otherwise, the port is just bound to the loopback interface. Also, I
    would suggest opening the tunnel on an internal host as opposed to doing it
    directly on the firewall.

    My $.02

    - Braden

  • Next message: Nicholas Nam: "RE: some tunnelling help needed"

    Relevant Pages

    • RE: X11 forwarding help
      ... "You could try setting up your own port redirection so that you can forward ... 6010 if they are in use already on intermediate and remote hosts. ... > I'm using ssh to do X11 forwarding over a gateway and it seems to work ... On the server, try setting X11UseLocalhost no ...
      (SSH)
    • Re: some tunnelling help needed: README FIRST
      ... > You forgot the '-g' option, to allow remote hosts to connect to the local ... the port is just bound to the loopback interface. ... For GNU/Linux Success Stories and Articles visit: ...
      (SSH)
    • Re: X11 forwarding help
      ... > "You could try setting up your own port redirection so that you can forward ... > back to the first tunnel that you set up. ... > 6010 if they are in use already on intermediate and remote hosts. ... the endpoint of the remote port tunnel will be bound ...
      (SSH)
    • Re: SSH: only listens on loopback
      ... -g Allows remote hosts to connect to local forwarded ports. ... rich said: ... > BUT, the 8080 port is only open to the local host, and I want it open for all. ...
      (Debian-User)
    • Re: How do I port forward through 2 remote hosts?
      ... > tunnel through port 119. ... port 119" does not mean anything. ... NNTP server running on C. ... > remote hosts to accept tunnelling of port 119 through themselves. ...
      (comp.security.ssh)
    • Quantcast