Results 1 to 5 of 5

Thread: SSH tunneling problem

  1. #1
    Join Date
    Dec 2008
    Beans
    5

    SSH tunneling problem

    Hello,

    I have a problem with setup of SSH tunneling, I making tunnel in local machine with:

    Code:
    ssh -v -N -R 2222:localhost:22 user@<public ip>
    tunnel looks proper established:

    Code:
    debug1: remote forward success for: listen 2222, connect localhost:22
    I can connect to tunnel using remote machine with localhost:

    Code:
    nc -zv localhost 2222
    Connection to localhost (::1) 2222 port [tcp/*] succeeded!
    but cannot using my public ip:

    Code:
    nc -zv <public ip> 2222
    nc: connect to <public ip> port 2222 (tcp) failed: Connection refused
    Ports looks open:

    Code:
    netstat -lntu
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State
    tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN
    tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
    tcp        0      0 127.0.0.1:2222          0.0.0.0:*               LISTEN
    tcp6       0      0 ::1:2222                :::*                    LISTEN
    tcp6       0      0 :::80                   :::*                    LISTEN
    tcp6       0      0 :::22                   :::*                    LISTEN
    tcp6       0      0 :::21                   :::*                    LISTEN
    udp        0      0 127.0.0.53:53           0.0.0.0:*
    Code:
    lsof -i :2222
    COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    sshd    4847  fjk    7u  IPv6  53081      0t0  TCP localhost:2222 (LISTEN)
    sshd    4847  fjk    9u  IPv4  53082      0t0  TCP localhost:2222 (LISTEN)
    I'm also set tcpforwarding in /etc/ssh/sshd_config:

    Code:
    AllowTcpForwarding yes
    What I'm doing wrong?
    Rehards.

  2. #2
    Join Date
    Oct 2023
    Beans
    2

    Re: SSH tunneling problem

    By default, it will listen on localhost (loopback interface) only. You need to specify the bind_address as 0.0.0.0 in your command:

    Code:
    ssh -R 0.0.0.0:2222:localhost:22 TARGET -N
    https://serverfault.com/a/861911

  3. #3
    Join Date
    Dec 2008
    Beans
    5

    Re: SSH tunneling problem

    THANKS! Now it works fine.

  4. #4
    Join Date
    Dec 2008
    Beans
    5

    Re: SSH tunneling problem

    Is there any way to have real IP's in logs? Now all incoming connections from that tunnel to sshd or Apache are logged as 127.0.0.1 :/
    So I cannot use fail2ban for example
    Last edited by fjk8; 2 Weeks Ago at 11:39 AM.

  5. #5
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: SSH tunneling problem

    I do port translation on the router, not the VM host. My VMs have their own LAN IPs.

    Also, I use non-standard ports for WAN-side ssh connections. They do get found, but instead of 10,000 attempts/hour, I see just 150 attempts/day. Fail2ban works. For example, my logwatch reporting .., from yesterday:
    Code:
    Banned services with Fail2Ban:                             Bans:Unbans
        sshd:                                                   [128:85 ]
    And bans for bots scanning my reverse proxy system:

    Code:
     Banned services with Fail2Ban:                              Bans:Unbans
        nginx-botsearch:                                        [  3:3  ]
    I have different systems for external access for specific reasons.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •