FS#67742 - [openssh]Really slow speed while transfering a file with scp or sftp.

Attached to Project: Arch Linux
Opened by Frederic Bezies (fredbezies) - Friday, 28 August 2020, 10:23 GMT
Last edited by David Runge (dvzrv) - Tuesday, 05 September 2023, 10:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Levente Polyak (anthraxx)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I can't get more than 800kbps/s after testing on many machines using ArchLinux in upload with scp or sftp.

Tests in virtual machines from Ubuntu or debian or Fedora show a maximum upload line speed of 64MB/s.

To check I tested Manjaro or Arch in virtual machine and even bug less than 1mo/s in upload.


Additional info:
openssh 8.3p1-3

Steps to reproduce:
This task depends upon

Closed by  David Runge (dvzrv)
Tuesday, 05 September 2023, 10:24 GMT
Reason for closing:  Upstream
Additional comments about closing:  If this is still considered a bug, please convince upstream to fix this, as applying long-running patches is super painful and not the Arch way.
Comment by loqs (loqs) - Saturday, 29 August 2020, 17:11 GMT
If you build the same version of openssh Arch uses with the locally applied patches on Ubuntu / Debian / Fedora what speed does that produce?
What about the reverse the package as the other distributions shipped it, built on Arch?
Comment by Frederic Bezies (fredbezies) - Saturday, 29 August 2020, 17:33 GMT
As far as I know, it works with Ubuntu 20.04 (Openssh 8.2) and the one for Ubuntu 20.10 (Openssh 8.3), but it doesn't with Fedora 32 (Openssh 8.3). All these distributions were tested in docker environment.

This bug can be seen with all Openssh 8.xx version in Archlinux.
Comment by loqs (loqs) - Saturday, 29 August 2020, 17:51 GMT
What if you force Ubuntu / Debian to use the same IPQoS as Arch / Fedora? [1]
If not [2] [3] [4] contain patches uses by Debian Fedora and Arch respectively.
Edit:
I think the following should change the IPQoS to the settings Arch / Fedora use.
ssh -o IPQoS='af21 cs1'

[1] https://sources.debian.org/src/openssh/1:8.2p1-4/debian/patches/revert-ipqos-defaults.patch/
[2] https://sources.debian.org/src/openssh/1:8.2p1-4/debian/patches/
[3] https://src.fedoraproject.org/rpms/openssh/tree/master
[4] https://github.com/archlinux/svntogit-packages/tree/packages/openssh/trunk
Comment by Frederic Bezies (fredbezies) - Saturday, 29 August 2020, 19:31 GMT
If I add 'ssh -o IPQoS='af21 cs1' -> this makes the bug appear on Debian. It looks like you nailed the bug.

Edit: if I applied Debian patch "revert-ipqos...", it fixes the bug.
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 29 October 2020, 21:23 GMT
This bug does seem to happen only on very particular scenarios, like described on the debian patch, it seems to affect only when you're interacting with iptables and some virtualization, I guess docker would trigger these too. I'm not very fond of applying this patch to Arch package.
Comment by Giancarlo Razzolini (grazzolini) - Saturday, 10 April 2021, 12:36 GMT
Is this still happening with openssh 8.5?
Comment by Thomas Lübking (luebking) - Tuesday, 05 July 2022, 14:34 GMT
@grazzolini, it's (apparently still) happening w/ 9.0p1 - https://bbs.archlinux.org/viewtopic.php?pid=2044567#p2044567
Updated patch source, https://salsa.debian.org/ssh-team/openssh/-/blob/master/debian/patches/revert-ipqos-defaults.patch
https://github.com/archlinux/svntogit-packages/blob/packages/openssh/trunk/PKGBUILD sed's /etc/ssh/sshd_config so maybe sed'ding /etc/ssh/ssh_config would be an acceptable alternative to the patch?
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...