SSH access closed after update to 4.62

I cofigured SSH enabled earlier and SSH worked flawlessly.
But after update, SSH access was closed.

I first tried inside the LAN but got Connection to 10.0.0.1 closed. I configured the LAN subnet as 10.0.0.0/24 before which still worked as I could access ther web interface as before.
And I could also access the web interface from the WAN by using another port. So that was no issue.
But connecting with ssh root@10.0.0.1 resulted in Connection to 10.0.0.1 closed. Now I opened SSH access via WAN (which is inside another LAN), but got the same message.
I did not change any SSH setting before update.
How can I recover SSH access ?

Here my SSH session (-vvv == extensive debug info):

armemac.local:~/scratch % ssh  -p 22 -vvv root@192.168.0.36
OpenSSH_9.6p1, LibreSSL 3.3.6
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no files
debug1: /etc/ssh/ssh_config line 54: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.0.36 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/Users/klaas/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/Users/klaas/.ssh/known_hosts2'
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to 192.168.0.36 [192.168.0.36] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /Users/klaas/.ssh/id_rsa type 0
debug1: identity file /Users/klaas/.ssh/id_rsa-cert type -1
debug1: identity file /Users/klaas/.ssh/id_ecdsa type -1
debug1: identity file /Users/klaas/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/klaas/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/klaas/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /Users/klaas/.ssh/id_ed25519 type 3
debug1: identity file /Users/klaas/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/klaas/.ssh/id_ed25519_sk type -1
debug1: identity file /Users/klaas/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/klaas/.ssh/id_xmss type -1
debug1: identity file /Users/klaas/.ssh/id_xmss-cert type -1
debug1: identity file /Users/klaas/.ssh/id_dsa type 1
debug1: identity file /Users/klaas/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.6
debug1: Remote protocol version 2.0, remote software version dropbear
debug1: compat_banner: no match: dropbear
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 192.168.0.36:22 as 'root'
debug3: record_hostkey: found key type ED25519 in file /Users/klaas/.ssh/known_hosts:178
debug3: load_hostkeys_file: loaded 1 keys from 192.168.0.36
debug1: load_hostkeys: fopen /Users/klaas/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01@openssh.com, using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,kexguess2@matt.ucc.asn.au
debug2: host key algorithms: ssh-ed25519,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes256-ctr
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes256-ctr
debug2: MACs ctos: hmac-sha1,hmac-sha2-256
debug2: MACs stoc: hmac-sha1,hmac-sha2-256
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:kz7Wvodo2y7IBKgP6QptL2ymDIQUixNxGxpfnFgxrQo
debug3: record_hostkey: found key type ED25519 in file /Users/klaas/.ssh/known_hosts:178
debug3: load_hostkeys_file: loaded 1 keys from 192.168.0.36
debug1: load_hostkeys: fopen /Users/klaas/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host '192.168.0.36' is known and matches the ED25519 host key.
debug1: Found key in /Users/klaas/.ssh/known_hosts:178
debug3: send packet: type 21
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,rsa-sha2-256,ssh-rsa>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug3: ssh_get_authentication_socket_path: path '/Users/klaas/.sekey/ssh-agent.ssh'
debug1: get_agent_identities: ssh_get_authentication_socket: Connection refused
debug1: Skipping ssh-dss key /Users/klaas/.ssh/id_dsa - corresponding algorithm not in PubkeyAcceptedAlgorithms
debug1: Will attempt key: /Users/klaas/.ssh/id_rsa RSA SHA256:Mh8uuwZwf0zVhPGPmZ/i7SVHlikZmAleGnj9kphNMts
debug1: Will attempt key: /Users/klaas/.ssh/id_ecdsa 
debug1: Will attempt key: /Users/klaas/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /Users/klaas/.ssh/id_ed25519 ED25519 SHA256:ZJ+grijrDZCBHEnwsNaU9tiMqLWuqXDEZDGBQfyU2Ss
debug1: Will attempt key: /Users/klaas/.ssh/id_ed25519_sk 
debug1: Will attempt key: /Users/klaas/.ssh/id_xmss 
debug2: pubkey_prepare: done
debug1: Offering public key: /Users/klaas/.ssh/id_rsa RSA SHA256:Mh8uuwZwf0zVhPGPmZ/i7SVHlikZmAleGnj9kphNMts
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/klaas/.ssh/id_ecdsa
debug3: no such identity: /Users/klaas/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /Users/klaas/.ssh/id_ecdsa_sk
debug3: no such identity: /Users/klaas/.ssh/id_ecdsa_sk: No such file or directory
debug1: Offering public key: /Users/klaas/.ssh/id_ed25519 ED25519 SHA256:ZJ+grijrDZCBHEnwsNaU9tiMqLWuqXDEZDGBQfyU2Ss
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/klaas/.ssh/id_ed25519_sk
debug3: no such identity: /Users/klaas/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /Users/klaas/.ssh/id_xmss
debug3: no such identity: /Users/klaas/.ssh/id_xmss: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
root@192.168.0.36's password: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Here password filled in 
debug3: send packet: type 50 
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 52
Authenticated to 192.168.0.36 ([192.168.0.36]:22) using "password".
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: filesystem
debug3: client_repledge: enter
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug3: send packet: type 98
debug1: Sending environment.
debug3: Ignored env TERM_PROGRAM
debug3: Ignored env SHELL
debug3: Ignored env TERM
debug3: Ignored env TMPDIR
debug3: Ignored env TERM_PROGRAM_VERSION
debug3: Ignored env TERM_SESSION_ID
debug3: Ignored env USER
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env PATH
debug3: Ignored env LaunchInstanceID
debug3: Ignored env __CFBundleIdentifier
debug3: Ignored env PWD
debug3: Ignored env XPC_FLAGS
debug3: Ignored env XPC_SERVICE_NAME
debug3: Ignored env SHLVL
debug3: Ignored env HOME
debug3: Ignored env LOGNAME
debug3: Ignored env SECURITYSESSIONID
debug3: Ignored env OLDPWD
debug3: Ignored env EDITOR
debug3: Ignored env LDFLAGS
debug3: Ignored env CPPFLAGS
debug3: Ignored env PKG_CONFIG_PATH
debug3: Ignored env LE_WORKING_DIR
debug3: Ignored env GUILE_LOAD_PATH
debug3: Ignored env GUILE_LOAD_COMPILED_PATH
debug3: Ignored env GUILE_SYSTEM_EXTENSIONS_PATH
debug3: Ignored env HOMEBREW_NO_AUTO_UPDATE
debug3: Ignored env AUTOJUMP_SOURCED
debug3: Ignored env AUTOJUMP_ERROR_PATH
debug1: channel 0: setting env LC_CTYPE = "UTF-8"
debug2: channel 0: request env confirm 0
debug3: send packet: type 98
debug3: Ignored env _
debug3: Ignored env __CF_USER_TEXT_ENCODING
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug3: client_repledge: enter
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 24576 rmax 32759
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i0 o1 sock -1 wfd 5 efd 6 [write])
debug2: channel 0: output drain -> closed
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: chan_shutdown_read: channel 0: (i0 o3 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 [session] r0 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1 io 0x00/0x00)

debug3: send packet: type 1
Connection to 192.168.0.36 closed.   <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Transferred: sent 2780, received 976 bytes, in 0.0 seconds
Bytes per second: sent 230342.2, received 80868.3
debug1: Exit status 1
armemac.local:~/scratch % 

Hi,

What is the router LAN IP? Is it 192.168.0.36?

No, that is the WAN IP (inside another LAN, hence the indoor IP).

But, now the SSH does work ! Very strange, I have turned the router off and a day later I turned it on and after repeated reboots or turn off / on the SSH (over the default Dropbear SSH) kept working normally.
I also saw that all packages I installed via opkg were still present, but only the /root folder was empty so .bashrc and .bash_history were gone, no big deal.
And the OpenSSH server was still present, but disabled, so I re-enabled it and it kept working after reboots.
Furthermore, the web interface is still the same and works awesome, just as before the update.
Only one thing which does not work: having internet on the clients when I have a VPN client enabled on the router, but that issue was already before the core update.
I'll open a separate topic for this.

1 Like