More on SSH tunnelling/forwarding. - SSH

This is a discussion on More on SSH tunnelling/forwarding. - SSH ; OK, I managed to get the following working: ---------------------------------------------------------------------------------------------------- A firewall between SERVER and CLIENT only allows TCP port 22 from SERVER to CLIENT (but not viceversa!) SERVER -------22------> CLIENT What I would like to achieve via ssh tunnelling is ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: More on SSH tunnelling/forwarding.

  1. More on SSH tunnelling/forwarding.

    OK,

    I managed to get the following working:

    ----------------------------------------------------------------------------------------------------
    A firewall between SERVER and CLIENT only allows TCP port 22 from
    SERVER to CLIENT (but not viceversa!)

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

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

    SERVER <-----1984------ CLIENT
    ------------------------------------------------------------------------------------------------------

    by running (on SERVER):
    $ ssh -f -N -R 1984:SERVER:1984 CLIENT


    Now I'd like to add the next (and last) bit of the configuration to the
    picture:

    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?
    Any security issues I shold be aware of?

    Thanks in advance

    Ciccio


  2. Re: More on SSH tunnelling/forwarding.

    Ciccio 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

  3. Re: More on SSH tunnelling/forwarding.

    Hi Paul,


    I ran that on CLIENT, then i logged onto GOOFY but I got the following
    error message

    [GOOFY]$ telnet localhost 1984
    Trying 127.0.0.1...
    telnet: Unable to connect to remote host: Connection refused

    What am I missing this time?

    Ciccio


+ Reply to Thread