[SOLVED] SSH typing delay

bitfuzzy · 01-30-2020, 07:01 AM

I've got 2 new dell laptops running Slackware current generally using ssh to connect to my servers running Slackware 14.1 and everything is fine.

However this morning I connected "to" one the Slackware current laptops and upon logging in I noticed that there's a distinct delay in typing. It's not much, but noticeable.

SSH to a machine other other than one running Slackware Current is fine.

SSH (from) Laptop 1 - running Slackware Current (to) Laptop 2 - running Slackware Current - results in the same typing delay

Any Ideas?

upnort · 01-30-2020, 11:22 AM

These systems are all on the same network subnet? I work remotely and commonly witness latency issues because of the distances. I never see latency issues on the home network where everything is on the same subnet and is local.

Edit: My memory is vague, but I remember weird latency issues with mc some years ago. I don't remember the root cause. I'm throwing out fuzzy guesses, but perhaps something to do with DNS or IPv6 or something like that. Perhaps something similar here. The latency is caused by some kind of lookup.

Have your tried SSH with lots of verbosity?

tramtrist · 01-30-2020, 11:31 AM

I have noticed this on my x270 lenovo ssh'ing into a Ryzen 5 box I built. After entering the session on the Ryzen box there is latency. I tried changing a bunch of SSHd options but nothing helped. It's not crippling just annoying..

bitfuzzy · 01-30-2020, 12:08 PM

Quote:

Originally Posted by upnort

These systems are all on the same network subnet?

Yea, they are and it's only when connected "to" slack-current

Quote:

After entering the session on the Ryzen box there is latency. I tried changing a bunch of SSHd options but nothing helped. It's not crippling just annoying..

Exactly... Very annoying

bitfuzzy · 01-30-2020, 01:03 PM

Quote:

Originally Posted by upnort

The latency is caused by some kind of lookup.

Have your tried SSH with lots of verbosity?

Yea compared the results between two connections from the same machine

1 - to a Slackware 14.1 box

1 - to a slack-current laptop

Other than expected differences (SSH version numbers, etc) there weren't any differences

mishehu · 01-30-2020, 04:37 PM

The only time I experience any delay on any of my systems that are on the same LAN segment is when one or both are wireless. The wired ones are without any delay at all. I am running -current, but I don't recall ever having delay within my LAN on wired-only connections. And even that delay that I have to/from wifi - it's typically < 100 ms.

tramtrist · 01-30-2020, 07:32 PM

Can confirm my setup is wireless to wireless...

mishehu · 01-30-2020, 07:35 PM

How much latency would you say there is?

bassmadrigal · 01-30-2020, 07:44 PM

I have a wireless to wireless and have never seen any noticeable latency except for sometimes when I'm coming in from the internet. I have several different types of methods for ssh, all wireless (I don't currently have anything wired on my network. I have a 14.2 wireless machine, a -current wireless machine, Windows 10 running Ubuntu using Windows Subsystem for Linux wireless, and my Android phone using JuiceSSH both wireless and mobile data (my server is internet facing and I can ssh into it). I frequently use my Windows 10 laptop and Android phone to ssh into my 14.2 and -current machines. I'll also use my 14.2 machine to ssh into my -current machine, but I rarely use -current to ssh into anything else as it is mainly an htpc that is hooked up to my tv and I have kodi start up automatically and just use a remote to interact with kodi. It doesn't have a keyboard hooked up normally.

bitfuzzy · 01-31-2020, 01:41 AM

Testing

bitfuzzy · 01-31-2020, 02:30 AM

This does appear to be related to wireless under Slackware Current

Wireless -Current / Wireless -Current
From -Current to -Current = Delayed typing

Wireless NON-Current / Wireless -Current
From NON-Current to -Current = Delayed typing
From -Current to NON-Current = No issue
From NON-Current to NON-Current = No issue

Wired NON-Current / Wireless -Current
From NON-Current to -Current = Delayed typing
From -Current to NON-Current = No issue
From NON-Current to NON-Current = No issue

Wired NON-Current / Wired -Current
From NON-Current to -Current = No issue
From -Current to NON-Current = No issue
From NON-Current to NON-Current = No issue

Wireless NON-Current / Wired -Current
From NON-Current to -Current = No issue
From -Current to NON-Current = No issue
From NON-Current to NON-Current = No issue

Wired -Current / Wired -Current
From -Current to -Current = No issue

bitfuzzy · 01-31-2020, 02:35 AM

Quote:

Originally Posted by mishehu

How much latency would you say there is?

It depends on how fast you type. If you hen peck you might not notice it.
It's enough to get on your nerves, but not enough to prevent you from getting anything accomplished

bitfuzzy · 01-31-2020, 03:10 AM

I may have found the fix (or at least a patch) to the issue by turning "off" the power saving feature on my wireless adapter

If you're using Networkmanager create a file named "wifi-powersave-off.conf" under /etc/NetworkManager/conf.d/

open the file and add:

Code:

# File to be place under /etc/NetworkManager/conf.d
[connection]
# Values are 0 (use default), 1 (ignore/don't touch), 2 (disable) or 3 (enable).
wifi.powersave = 2

Save the changes and restart Networkmanager

Code:

/etc/rc.d/rc.networkmanager restart

So it's looking good, but if anyone could confirm it would be helpful

upnort · 01-31-2020, 02:44 PM

Ah, the infamous wifi powersave. Good find!

bitfuzzy · 01-31-2020, 03:20 PM

Quote:

Originally Posted by upnort

Ah, the infamous wifi powersave. Good find!

Thanks, I'm just wishing I didn't waste 3 days chasing my tail tearing my SSH config apart

Because of the other systems, it didn't dawn on me it could be wireless related until it was mentioned as a possibility.