[Solved] ssh (and other network issues)

atte · 2013-05-31 12:15:45

Hi

I have some problems with my laptop (blokhus) running crunchbang. It manifests itself in different ways that I believe are related, although that might be me jumping to conclusions:

1) When I ssh into my home server (vodskov, running debian wheezy) with wired lan, the connection dies after a while (about 10 minutes) with "Timeout, server vodskov not responding." I have a single ubuntu box on the network, and from it ssh works just fine, I left it on for hours and it was still up. I tried ssh to the server (over wifi) from another laptop running crunchbang and it seems to keep the connection fine. I don't have the .ssh/config file on that particular laptop. I've just renamed the file config_, will reboot problematic laptop and report back if it changes anything. The two installations are almost identical (all packages installed though a shared install.sh script), although the problematic on is a lenovo x61s and the ok one is a eee900...

2) When I listen to streaming music from my ISP's streaming service the playlist stops after about two or three songs.

3) Downloading files from the net (iceweasel) "sometimes" stops too, not sure if it's happening at the same time as the other two problems...

When the problem "kicks in" ssh freezes (times out and returns to the local terminal after a while) *exactly* at the same time that the streaming music stops. I can connect through ssh in a new terminal without problems right away. The problem also occurs if I *only* use ssh *or* listens to streaming music.

I tried to remedy the problem (but without success) with the following on the laptop:

atte@blokhus:~$ cat .ssh/config 
Host atte.dk
    ServerAliveInterval=60
Host vodskov
    ServerAliveInterval=60

And on the server I have this:

atte@vodskov:~$ grep Alive /etc/ssh/sshd_config 
TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 3

Hoping for some clever thought and things to try or logfiles to check, cause I really have no clue...

Thanks in advance!

Last edited by atte (2013-06-03 08:15:34)

xaos52 · 2013-05-31 13:18:42

Add options -vvv to the client ssh command, start it from a terminal window and log the debug info.
e.g. launch ssh client on blokhus with

ssh -vvv atte@vodskov 2>&1 | tee client.log

After it disconnected, post content of file client.log in the current dir.

atte · 2013-06-01 04:17:38

Just as an experiment I did the same, but on wifi. That didn't disconnect, even left it during the night. So it seems it's something with the wired connection.

Anyways, here's the info:

atte@blokhus:~$ cat client.log 
OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to vodskov [192.168.0.31] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/atte/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/atte/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/atte/.ssh/id_rsa-cert type -1
debug1: identity file /home/atte/.ssh/id_dsa type -1
debug1: identity file /home/atte/.ssh/id_dsa-cert type -1
debug1: identity file /home/atte/.ssh/id_ecdsa type -1
debug1: identity file /home/atte/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-4
debug1: match: OpenSSH_6.0p1 Debian-4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-4
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "vodskov" from file "/home/atte/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/atte/.ssh/known_hosts:32
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA 71:ff:bd:01:43:9d:65:5d:18:04:22:85:0d:ae:1f:67
debug3: load_hostkeys: loading entries for host "vodskov" from file "/home/atte/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/atte/.ssh/known_hosts:32
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "192.168.0.31" from file "/home/atte/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /home/atte/.ssh/known_hosts:51
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'vodskov' is known and matches the RSA host key.
debug1: Found key in /home/atte/.ssh/known_hosts:32
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/atte/.ssh/id_rsa (0xb94cfe70)
debug2: key: /home/atte/.ssh/id_dsa ((nil))
debug2: key: /home/atte/.ssh/id_ecdsa ((nil))
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/atte/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug2: input_userauth_pk_ok: fp 7f:7d:9a:50:fa:16:02:81:8b:1d:8b:b0:14:2d:f0:d7
debug3: sign_and_send_pubkey: RSA 7f:7d:9a:50:fa:16:02:81:8b:1d:8b:b0:14:2d:f0:d7
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to vodskov ([192.168.0.31]:22).
debug2: fd 5 setting O_NONBLOCK
debug3: fd 6 is O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: fd 3 setting TCP_NODELAY
debug3: packet_set_tos: set IP_TOS 0x10
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug3: Ignored env ORBIT_SOCKETDIR
debug3: Ignored env SSH_AGENT_PID
debug3: Ignored env SHELL
debug3: Ignored env TERM
debug3: Ignored env XDG_SESSION_COOKIE
debug3: Ignored env WINDOWID
debug3: Ignored env GNOME_KEYRING_CONTROL
debug3: Ignored env USER
debug3: Ignored env MPD_HOST
debug3: Ignored env LS_COLORS
debug3: Ignored env EASYABCDIR
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env PATH
debug3: Ignored env MAIL
debug3: Ignored env PWD
debug3: Ignored env EDITOR
debug3: Ignored env GNOME_KEYRING_PID
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug3: Ignored env SHLVL
debug3: Ignored env HOME
debug3: Ignored env LOGNAME
debug3: Ignored env DBUS_SESSION_BUS_ADDRESS
debug3: Ignored env LESSOPEN
debug3: Ignored env DISPLAY
debug3: Ignored env LESSCLOSE
debug3: Ignored env XAUTHORITY
debug3: Ignored env COLORTERM
debug3: Ignored env _
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Linux vodskov 3.2.0-4-486 #1 Debian 3.2.41-2+deb7u2 i586

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
Last login: Fri May 31 14:34:10 2013 from blokhus.local
atte@vodskov:~$ debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
debug1: client_input_channel_req: channel 0 rtype keepalive@openssh.com reply 1
Write failed: Broken pipe
atte@blokhus:~$

atte · 2013-06-02 15:00:04

Ok, some new tests.

Streaming audio over internet breaks up after 10 minutes over ethernet cable, tried with another cable but no difference.
Over wlan streaming works just fine.

So it seems it's not hardware and not ssh, right? Sounds like an ethernet driver issue or something like that, any idea how I could debug the ethernet connection?

atte@blokhus:~$ lspci | grep Ether
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)

atte · 2013-06-02 17:26:21

More news:

If i switch off wifi (hardware switch) ethernet works fine. Hmmmm.

Any idea why the wlan is breaking up the ethernet connection every 10 minutes?

Last edited by atte (2013-06-03 07:08:01)

atte · 2013-06-03 08:14:03

Hi again

I (kind of) solved the problem. I found the following script here, that goes in /etc/NetworkManager/dispatcher.d/99-wlan:

#!/bin/bash

if [ "$1" = "eth0" ]; then
    case "$2" in
        up)
            nmcli nm wifi off
            ;;
        down)
            nmcli nm wifi on
            ;;
    esac
fi

Basically it disables the wlan connection when the wired connection comes on, and enables it again when wired connection is of.

So there's still "something wrong" somewhere deeper in my system, but this hack covers it up without any negative side-effects for me.

xaos52 · 2013-06-03 11:52:31

OK.
Thanks for the feedback. smile

CrunchBang Linux

SEARCH

#1 2013-05-31 12:15:45

[Solved] ssh (and other network issues)

#2 2013-05-31 13:18:42

Re: [Solved] ssh (and other network issues)

#3 2013-06-01 04:17:38

Re: [Solved] ssh (and other network issues)

#4 2013-06-02 15:00:04

Re: [Solved] ssh (and other network issues)

#5 2013-06-02 17:26:21

Re: [Solved] ssh (and other network issues)

#6 2013-06-03 08:14:03

Re: [Solved] ssh (and other network issues)

#7 2013-06-03 11:52:31

Re: [Solved] ssh (and other network issues)

Board footer