Home Network Community > DSL Modem&Routers > Archer VR2600v - Outgoing SSH-Connection failed
< DSL Modem&Routers

Archer VR2600v - Outgoing SSH-Connection failed

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Archer VR2600v - Outgoing SSH-Connection failed

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer VR2600v - Outgoing SSH-Connection failed
Archer VR2600v - Outgoing SSH-Connection failed
2016-09-29 23:23:10
Model :

Hardware Version :

Firmware Version : 1.1.0 0.8.0 v004f.0 Build 160215 Rel.30334n

ISP : Telekom Germany

Hello,
I have new installed a Archer VR2600v. The connection to internet is ok. But I can't connect my servers in internet via SSH from Linux-Console behind that router.
[CODE]OpenSSH_6.7p1 Debian-5+deb8u3, OpenSSL 1.0.1t 3 May 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 188.40.80.7 [188.40.80.7] port 52022.
debug1: Connection established.
debug1: identity file /home/andreas/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/andreas/.ssh/id_rsa-cert type -1
debug1: identity file /home/andreas/.ssh/id_dsa type 2
debug1: key_load_public: No such file or directory
debug1: identity file /home/andreas/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/andreas/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/andreas/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/andreas/.ssh/id_ed25519 type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/andreas/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Debian-6
debug1: match: OpenSSH_6.6.1p1 Debian-6 pat OpenSSH_6.6.1* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr umac-64-etm@openssh.com none
debug1: kex: client->server aes128-ctr umac-64-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA 3e:97:2b:24:ee:7e:f1:fc:5d:6a:46:dd:3b:2b:88:26
debug1: Host '[188.40.80.7]:52022' is known and matches the RSA host key.
debug1: Found key in /home/andreas/.ssh/known_hosts:4
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/andreas/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to xxx.xxx.xxx.xxx ([xxx.xxx.xxx.xxx]:xxxxxx).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Sending environment.
debug1: Sending env LANG = de_DE.UTF-8
[/CODE]
It hangs up here and I came not on my server.
What's wrong on ther router?

Thanks

Wambui
  0      
 
  0      
 
#1
Options
1 Reply
Re:Archer VR2600v - Outgoing SSH-Connection failed
2017-01-10 05:17:04
I just found an answer, which works for me: through http://askubuntu.com/questions/344863/ssh-new-connection-begins-to-hang-not-reject-or-terminate-after-a-day-or-so-on; it looks like the issue is as discussed on http://savannah.gnu.org/maintenance/SshAccess/:

Another problem can arise when you are trying to connect from behind a broken NAT router. During session setup, after the password has been given, OpenSSH sets the TOS (type of service) field in the IP datagram. Some broken routers are known to choke on this. This type of broken router is thankfully very infrequently seen these days. The effect is that your session hangs indefinitely after you gave your password. Here is the example output from such an ssh session:


user@localhost:~$ ssh -vvv {user-name}@cvs.savannah.gnu.org OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config [...] Enter passphrase for key '{homedir}/.ssh/id_rsa': debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). [...] debug2: fd 5 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768

and from here on the session hangs.
That's is what happens for me...


The fix is to make ssh send all its traffic via netcat, because netcat won't set the TOS field. If netcat iis nstalled, issue the following command to test whether the netcat route solves your problem:


ssh -o "ProxyCommand nc %h %p" {user-name}@{host} It is unclear to me why the NAT is broken on such a new router...
Nieks
  0  
  0  
#2
Options

Information

Helpful: 0

Views: 670

Replies: 1

About Us
Press
Copyright © TP-Link Corporation Limited. All rights reserved.