SSH timing out

kevindd992002

Member
Dec 20, 2023
53
2
8
So the original setup of my pve was that it only had one Linux VLAN with the ff ip config:

vmbr.25
IP/CIDR: 192.168.25.2/24
Gateway IP: 192.168.25.1

When I SSH from a client in the 192.168.20.0/24 network to 192.168.25.2:22, obviously it goes through the router (opnsense) and everything is working fine.

Now, I decided to multi-home my pve with the ff Linux VLANs and ip config:

vmbr.20
IP/CIDR: 192.168.20.2/24
Gateway IP: NO GATEWAY

vmbr.21
IP/CIDR: 192.168.21.2/24
Gateway IP: NO GATEWAY

vmbr.23
IP/CIDR: 192.168.23.2/24
Gateway IP: NO GATEWAY

vmbr.25
IP/CIDR: 192.168.25.2/24
Gateway IP: 192.168.25.1

My problem is whenever I SSH from the same client in the 192.168.20.0/24 network to 192.168.25.2:22, it connects just fine but will timeout after maybe 30 seconds to 1 minute (I haven't timed it yet). I can reproduce this everytime.

When I SSH from the same client to 192.168.20.2:22 instead (source and destination in the same network), I have no issues. Obviously, this is not layer 3 so the router is out of the question in this case.

Thoughts?
 
if you use an Ubuntu 24.04 client and open a terminal to connect to a server and then the connection is terminated after an indefinite period of time.
Take a look at “sudo dmesg -w” in the other terminal on the client.
I have errors that are disconnecting me.
But I don't have that on an Ubuntu 22.04.
Could therefore also be a client problem.
 
if you use an Ubuntu 24.04 client and open a terminal to connect to a server and then the connection is terminated after an indefinite period of time.
Take a look at “sudo dmesg -w” in the other terminal on the client.
I have errors that are disconnecting me.
But I don't have that on an Ubuntu 22.04.
Could therefore also be a client problem.
I actually use Putty in Windows. The timeout happens literally a few seconds after logging in. When this happens and I key in any input from the keyboard, I get this:

Network Error: Software caused connection abort


While I'm trying to recreate this issue, I have a cmd window open and a continuous ping to the same 192.168.25.2 address. I don't see any disconnects. So this problem is isolated to SSH and not the whole network of the pve.
 
You can install mtr on windows and use it to create a live traceroute to your IP.
mtr -t 192.168.xx
To me it sounds like a response packet is not being sent over the same route or network connection. and then the connection is terminated.
 
You can install mtr on windows and use it to create a live traceroute to your IP.
mtr -t 192.168.xx
To me it sounds like a response packet is not being sent over the same route or network connection. and then the connection is terminated.
If it was asymmetric routing, why would ping not drop?
 
I just found out that the Linux VLAN's that I added is what's causing the issue. Maybe because of the asymmetric routing that you were saying but don't understand why. Any ideas?
 
Last edited: