1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Asus RT-N16: SSH port forwarding not working in current Tomato releases

Discussion in 'Tomato Firmware' started by olli_h, Jan 26, 2012.

  1. olli_h

    olli_h Networkin' Nut Member

    After upgrading to tomato-K26USB-1.28.RT5x-MIPSR2-083V-AIO I get an error messsage when trying to use ssh with port forwarding to access a computer in my local network from WAN (ssh remote port forwarding IS enabled in the administration settings). To check if this is specific for the shibby build I did a compile from git which has the same problem:

    putty.log

    2012-01-26 11:08:48Looking up host "xxxxxxx.xxxxx.xxx"
    2012-01-26 11:08:48Connecting to xxx.xxx.xxx.xxx port 2222
    2012-01-26 11:08:48Server version: SSH-2.0-dropbear_0.53.1
    2012-01-26 11:08:48Using SSH protocol version 2
    2012-01-26 11:08:48We claim version: SSH-2.0-PuTTY_Snapshot_2012_01_25:r9376
    2012-01-26 11:08:48Using Diffie-Hellman with standard group "group14"
    2012-01-26 11:08:48Doing Diffie-Hellman key exchange with hash SHA-1
    2012-01-26 11:08:50Host key fingerprint is:
    2012-01-26 11:08:50ssh-rsa 1039 f0:2a:ea:18:c5:71:0e:3c:33:0a:b5:19:a0:74:09:d8
    2012-01-26 11:08:50Initialised AES-256 SDCTR client->server encryption
    2012-01-26 11:08:50Initialised HMAC-SHA1 client->server MAC algorithm
    2012-01-26 11:08:50Initialised AES-256 SDCTR server->client encryption
    2012-01-26 11:08:50Initialised HMAC-SHA1 server->client MAC algorithm
    2012-01-26 11:08:50Reading private key file "C:\Users\oh\SSHKeys\rsa-key-oh-RT-N16.ppk"
    2012-01-26 11:09:03Offered public key
    2012-01-26 11:09:03Offer of public key accepted
    2012-01-26 11:09:05Sent public key signature
    2012-01-26 11:09:05Access granted
    2012-01-26 11:09:05Opened channel for session
    2012-01-26 11:09:05Local port 80 forwarding to 192.168.118.111:80
    2012-01-26 11:09:05Local port 3391 forwarding to 192.168.118.111:3391
    2012-01-26 11:09:05Local port 10000 forwarding to 192.168.118.111:10000
    2012-01-26 11:09:05Local port 20000 forwarding to 192.168.118.111:20000
    2012-01-26 11:09:05Allocated pty (ospeed 38400bps, ispeed 38400bps)
    2012-01-26 11:09:05Started a shell/command
    2012-01-26 11:09:21Opening forwarded connection to 192.168.118.111:10000
    2012-01-26 11:09:21Forwarded connection refused by server: Connect failed []
    2012-01-26 11:09:21Opening forwarded connection to 192.168.118.111:10000
    2012-01-26 11:09:21Forwarded connection refused by server: Connect failed []
    2012-01-26 11:09:21Opening forwarded connection to 192.168.118.111:10000
    2012-01-26 11:09:24Forwarded connection refused by server: Connect failed []
    2012-01-26 11:09:24Opening forwarded connection to 192.168.118.111:10000
    2012-01-26 11:09:25Forwarded connection refused by server: Connect failed []
    2012-01-26 11:09:25Opening forwarded connection to 192.168.118.111:10000
    2012-01-26 11:09:34Forwarded connection refused by server: Connect failed []

    This was working in the orginal Teddy build 54 from Nov 2010 and in a version I build from git in April 2011. Everything else is working fine...

    Any ideas?
     
  2. Toastman

    Toastman Super Moderator Staff Member Member

    Would appear that it reached the server and got a reply, as it was refused.
     
  3. olli_h

    olli_h Networkin' Nut Member

    Yes, but I think the server refusing the connection is SSH/Dropbear running on the RT-N16. Besides the newer firmware nothing changed in my setup...
     
  4. olli_h

    olli_h Networkin' Nut Member

    ... which is actually not true as the target server has been moved to another subnet. My problem, sorry...
     

Share This Page