Good catch, Seth :-).
Apparently this topic has been discussed in the past in bug #1822370 and
https://lists.debian.org/debian-devel/2019/04/msg00010.html. Those
discussions resulted in the decision to revert the IPQoS default values
from openssh, which is something we're still doing. The
Alvaro, thanks for reporting back! I'm glad it worked.
I don't know the full details of which QoS settings changed in which
releases, but this email suggests that there was active interest in
changing which exact values were used:
http://lists.mindrot.org/pipermail/openssh-unix-
Morning Seth,
You hit the right key! Adding to ssh_config:
IPQoS none
now it works correctly:
acs@lsp-022:~$ ssh -T g...@github.com
Hi acs! You've successfully authenticated, but GitHub does not provide shell
access.
With the default value (lowdelay) it just not connect.
With
Alvaro, I wonder if your network is dropping packets with unexpected IP
QoS flags? Look for 'IPQoS' in ssh_config(5) to see the defaults and
available choices. This would be influenced by ssh settings but still
operate at TCP level.
Thanks
--
You received this bug notification because you are a
Hi Paride,
Ok, nice to hear that it is just an issue with my config.
I will try to isolate the issue and if the result is interesting, report
it in this issue.
Thanks you for your awesome work with Ubuntu.
Cheers
-- Alvaro
--
You received this bug notification because you are a member of
Hello Alvaro and thanks for this bug report. We have many systems
running Jammy and they're able to connect to GitHub with no issues. I
also tried with GitLab.com and it works just fine. This is not to
dismiss your report, but there's clearly something else involved in the
problem you're hitting.
Hi Seth,
Yes, I know it seems to be a problem with the TCP connection, but it is
not:
```
acs@lsp-022:~$ nc github.com 22
SSH-2.0-babeld-78a8149e
```
```
acs@lsp-022:~$ nc gitlab.com 22
SSH-2.0-OpenSSH_8.4p1 Debian-5
```
```
acs@lsp-022:~$ ssh -Tv g...@github.com
OpenSSH_8.9p1 Ubuntu-3,
