SSH is getting blocked between FreeNAS 11.3 machines

Description

Got one successful replication done manually. When the next replication was attempted on a schedule it and subsequent replications have failed to complete because SSH is no longer completing between the hosts.

SSH from putty at 10.10.30.1 to 10.10.30.253 works

SSH from openssh at 10.10.30.1 to 10.10.30.253 works

SSH from freenas at 10.10.30.254 to 10.10.30.253 does not elicit a login prompt, but does accept a tcp connection

SSH from freenas at 10.10.30.253 to 10.10.30.253 works

Replication error log is attached.

SSH log is as follows:

tunneldevice any:any
controlpersist no
escapechar ~
ipqos lowdelay throughput
rekeylimit 0 0
streamlocalbindmask 0177
root@officenas[~]# ssh -v 10.10.30.253
OpenSSH_7.5p1, OpenSSL 1.0.2s-freebsd 28 May 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.10.30.253 [10.10.30.253] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_rsa type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: Fssh_key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.5 FreeBSD-20170903
debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0-hpn14v15
debug1: match: OpenSSH_8.0-hpn14v15 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 10.10.30.253:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

And then after a long wait, I also get:

Connection closed by 10.10.30.253 port 22

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Daniel Lynes

October 1, 2020 at 5:29 PM

The GRE tunnel used in this case specifically is an EoIP tunnel.

Daniel Lynes

October 1, 2020 at 5:28 PM

Determined why this and ssh were not working. Apparently it's having an issue working over a GRE tunnel. I'm not sure why that is, but after I disabled the GRE tunnel, everything's working fine.

William Gryzbowski

September 28, 2020 at 2:02 PM

I definitely do not how what to do with this ticket since it appears to be a local/network issue from where I am seeing.

There is nothing special in FreeNAS that would make it behave differently, its simply OpenSSH with no modifications.

We don't really have resources to diagnose edge case issues like yours unless there is some indication that this is affecting multiple people and/or there is a realiable reproduction scenario we can use.

Daniel Lynes

September 21, 2020 at 4:50 PM

I've tested smbfs on FreeNAS terminal, Linux (Ubuntu 20.04), Debian Buster, Windows 10, MacOS High Sierra, MacOS Catalina

Daniel Lynes

September 21, 2020 at 4:49 PM

Also, Bonnie, seeing as how you have the full debug logs, I'll mention a couple of other things as well:

some macs when attempting to store a file on NFS, FreeNAS will create multiple 0 byte copies of the file. Even the first copy of the original file will be 0 bytes.
smbfs only properly works on the local network and even then only with a hostname; ip address only shows the Resource share and not the Work share, no matter whether it's on the same lan or on a routed network
never did get afs to work, but I suspect that's more of a misunderstanding on my part as to how afs gets configured and how it works

Resize issue view side panel

User Configuration Error

Details

Assignee

Triage Team

Reporter

Daniel Lynes

Labels

Impact

Critical

Priority

Low

More fields

Katalon Platform

Created September 20, 2020 at 11:53 PM

Updated July 1, 2022 at 4:55 PM

Resolved October 1, 2020 at 6:17 PM

SSH is getting blocked between FreeNAS 11.3 machines

Description

Problem/Justification

Impact

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Details

Assignee

Reporter

Labels

Impact

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform