Re: More on SSH tunnelling/forwarding.

Ciccio <lserena@xxxxxxxxx> wrote:

There is another firewall between CLIENT and GOOFY, again only
allowing TCP port 22 from CLIENT to GOOFY (and NOT viceversa!):

SERVER -------22------> CLIENT -------22-------> GOOFY

What I would like to achieve via ssh tunnelling is to send TCP port
1984 traffic from GOOFY to SERVER (through CLIENT):

SERVER <-----1984----- CLIENT
SERVER <----------------(CLIENT)----------1984------ GOOFY

Please note that:
a. the remote forwarding of 1984 from CLIENT to SERVER is already
working;
b. there is no native process on CLIENT listening on port 1984.

So, how do I do that?

Run `ssh -f -N -R 1984:127.0.0.1:1984 GOOFY` on CLIENT.

Paul
.

Relevant Pages

  • SUMMARY: Slightly off topic | Two-hops SSH tunnelling.
    ... A firewall between SERVER and CLIENT only allows TCP port 22 from ... There is another firewall between CLIENT and GOOFY, ... If you are not the intended recipient be aware that any ...
    (SunManagers)
  • Re: VPN setup with static IP. How?
    ... That means the server didn't answer. ... do you have tcp port 1723 forwarded to ... >> on the client machine to use pptp rather than automatic. ...
    (microsoft.public.windows.server.networking)
  • Two-hops SSH tunnelling
    ... A firewall between SERVER and CLIENT only allows TCP port 22 from ... What I would like to achieve via ssh tunnelling is to send TCP port ... There is another firewall between CLIENT and GOOFY, ...
    (SSH)
  • Re: RWW Issues When Connecting from WAN Side
    ... LAN (XP Pro Client connecting to Server via RWW) ... - Lots of traffic on TCP port 4125 ... WAN (XP Pro Client trying to connect to Server/Client via RWW) ...
    (microsoft.public.windows.server.sbs)
  • Slightly off topic | Two-hops SSH tunnelling.
    ... A firewall between SERVER and CLIENT only allows TCP port 22 from ... What I would like to achieve via ssh tunnelling is to send TCP port ... There is another firewall between CLIENT and GOOFY, ...
    (SunManagers)