Unable to SSH to nodes

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
redmonds
Posts: 2
Joined: Tue Feb 28, 2023 10:12 pm

Unable to SSH to nodes

Post by redmonds » Thu Jul 25, 2024 12:35 pm

I am running EVE Pro an a Dell R810 with 2 x Intel Xeon E7-4780s each with 40 cores, 128GB of RAM, a 2TB HD and one NIC connected to the network. I have a management network which currently just has a switch image (Arista vEOS-Lab v4.30.7M) that connects to the network and a Cloud9 network. The management switch is serving DHCP out interface Ethernet1 to the Cloud9 network, where the management connections for my other labs connect. It also acts as the router to get to the other labs. I am able to SSH to the management switch but not to anything beyond it. I can ping all the devices. The really strange thing is, when I attempt SSH, I see a response coming all the way back to my laptop, but no session will open. I am also unable to SSH from the management switch to any of the devices. This worked right after I installed v6.2.0-4, but then quit working for no apparent reason.

Here are the outputs from the tcpdump and ssh -vT commands:

Code: Select all

$ tcpdump -i en0 host 172.16.0.31
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on en0, link-type EN10MB (Ethernet), snapshot length 524288 bytes
07:26:04.026559 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211482721 ecr 0,sackOK,eol], length 0
07:26:04.031658 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516753999 ecr 2211482721,nop,wscale 7], length 0
07:26:05.028076 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211483723 ecr 0,sackOK,eol], length 0
07:26:05.033778 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516755000 ecr 2211482721,nop,wscale 7], length 0
07:26:05.034831 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516755002 ecr 2211482721,nop,wscale 7], length 0
07:26:06.029928 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211484724 ecr 0,sackOK,eol], length 0
07:26:06.036634 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516756002 ecr 2211482721,nop,wscale 7], length 0
07:26:07.030328 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211485725 ecr 0,sackOK,eol], length 0
07:26:07.036147 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516757003 ecr 2211482721,nop,wscale 7], length 0
07:26:08.031559 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211486726 ecr 0,sackOK,eol], length 0
07:26:08.038408 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516758004 ecr 2211482721,nop,wscale 7], length 0
07:26:09.032528 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211487727 ecr 0,sackOK,eol], length 0
07:26:09.040244 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516759008 ecr 2211482721,nop,wscale 7], length 0
07:26:11.032441 IP 192.168.10.77.60950 > 172.16.0.31.ssh: Flags [S], seq 2023825016, win 65535, options [mss 1460,nop,wscale 6,nop,nop,TS val 2211489727 ecr 0,sackOK,eol], length 0
07:26:11.042442 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516761009 ecr 2211482721,nop,wscale 7], length 0
07:26:13.066154 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516763032 ecr 2211482721,nop,wscale 7], length 0
07:26:17.096896 IP 172.16.0.31.ssh > 192.168.10.77.60950: Flags [S.], seq 3942685690, ack 2023825017, win 65160, options [mss 1460,sackOK,TS val 1516767064 ecr 2211482721,nop,wscale 7], length 0
...

Code: Select all

$ ssh -vT admin@172.16.0.31
OpenSSH_9.8p1, OpenSSL 3.3.1 4 Jun 2024
debug1: Reading configuration data /Users/redmonds/.ssh/config
debug1: /Users/redmonds/.ssh/config line 184: Applying options for *
debug1: Reading configuration data /opt/homebrew/etc/ssh/ssh_config
debug1: Connecting to 172.16.0.31 [172.16.0.31] port 22.
Any suggestions are welcome.

Thanks.

Uldis (UD)
Posts: 5177
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Unable to SSH to nodes

Post by Uldis (UD) » Thu Jul 25, 2024 7:43 pm

Upgrade your EVE to 6.2.0-6 and do

Code: Select all

systemctl stop tomcat9
sleep 1
rm -fr /var/lib/tomcat9/webapps/guacamole
sleep 1
systemctl start tomcat9


unl_wrapper -a backupdb
unl_wrapper -a restoredb
reboot after

make sure you cleaned your browser cache and cookies

redmonds
Posts: 2
Joined: Tue Feb 28, 2023 10:12 pm

Re: Unable to SSH to nodes

Post by redmonds » Tue Jul 30, 2024 7:39 pm

Thanks. I did all that with no change. Guess I'm going to have to trunk my server connection to my LAN switch and serve DHCP from my firewall like I do with the rest of my network.

Thanks for the help though.

Post Reply