Ah, interesting. I tried your suggestion, and I get the message
Disconnecting: listen: Bad file descriptor
when I run it. Inspection shows this is being generated by sshd on
machine b (the outside firewall):
Jan 14 00:04:39 firewall sshd[14436]: fatal: Received disconnect: listen:
Bad file descriptor
So I wonder what that means?
P.
On Fri, 14 Jan 2000, Atro Tossavainen wrote:
> Hello Phil,
>
> > Now, a user on the outside machine (a) can use ssh to gain access directly to
> > the web server (d) like this:
> >
> > # ssh b ssh c ssh d
> >
> > that works great for a shell session.
> >
> > Now how can I run a web connection over this? ssh has the ability to forward
> > local ports to remote ports, but I can't figure out if that works over
> > multiple ssh connections like I have. I want to do something like (from a):
> >
> > # ssh -L 1234:d:80 ssh b ssh c
> >
> > So that traffic from local port 1234 ends up on port 80 of the web
> > server.
>
> But the firewall(s) in between b and d block the HTTP traffic. B tries
> to send it in the clear since your tunneling is in between a and b.
> With multiple connections, you need to perform multiple tunnelings.
>
> a% ssh -L X:b:Y b ssh -L Y:c:Z c ssh -L Z:d:80 d
>
> where X, Y and Z are any available high-numbered ports on the hosts
> a, b and c.
>
> Hope this helps.
>
>
