SSH “lag” in LAN on some machines, mixed distros
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I've had a strange problem with SSH connections inside my LAN for a few months. It only happens when I'm using my Windows 10 device to connect to a (barebone) linux machine.
When I connect to a SSH server it's like my input is only sent once every second. If I hold a key, it doesn't print anything for a second and after that second I see every keystroke I did during that time.
This is how it looks on the working servers:
This is how it looks on the ones with the issue:
Things I have tested/found out
- Changing the "UseDNS" setting in /etc/sshd doesn't fix it
- It happens with bash (and zsh) on Debian (OpenSSH_7.4p1 Debian-10+deb9u6, OpenSSL 1.0.2r 26 Feb 2019) and Ash on Alpine Linux (OpenSSH_7.9p1, OpenSSL 1.1.1b 26 Feb 2019)
- It doesn't happen on Alpine Linux OpenSSH_7.7p1, LibreSSL 2.7.4
- It doesn't happen with every machine, just some (not depending on the distro)
- resolv.conf is correct
- Error happens with and without ClientAliveInterval (tested on client and server)
- Pinging the devices is always fast (less than 1 ms) so it's only SSH
- It also lags when I ssh from the linux subsystem on Windows 10 and with Putty and with MobaXterm
- No problems when I connect from Linux instead of Windows
Does anyone have any clues or things I could try?
Thanks
linux ssh windows-10 putty lag
asked Apr 4 at 19:32
ChristianChristian
116417
add a comment |
I've had a strange problem with SSH connections inside my LAN for a few months. It only happens when I'm using my Windows 10 device to connect to a (barebone) linux machine.
When I connect to a SSH server it's like my input is only sent once every second. If I hold a key, it doesn't print anything for a second and after that second I see every keystroke I did during that time.
This is how it looks on the working servers:
This is how it looks on the ones with the issue:
Things I have tested/found out
- Changing the "UseDNS" setting in /etc/sshd doesn't fix it
- It happens with bash (and zsh) on Debian (OpenSSH_7.4p1 Debian-10+deb9u6, OpenSSL 1.0.2r 26 Feb 2019) and Ash on Alpine Linux (OpenSSH_7.9p1, OpenSSL 1.1.1b 26 Feb 2019)
- It doesn't happen on Alpine Linux OpenSSH_7.7p1, LibreSSL 2.7.4
- It doesn't happen with every machine, just some (not depending on the distro)
- resolv.conf is correct
- Error happens with and without ClientAliveInterval (tested on client and server)
- Pinging the devices is always fast (less than 1 ms) so it's only SSH
- It also lags when I ssh from the linux subsystem on Windows 10 and with Putty and with MobaXterm
- No problems when I connect from Linux instead of Windows
Does anyone have any clues or things I could try?
Thanks
linux ssh windows-10 putty lag
asked Apr 4 at 19:32
ChristianChristian
116417
add a comment |
I've had a strange problem with SSH connections inside my LAN for a few months. It only happens when I'm using my Windows 10 device to connect to a (barebone) linux machine.
When I connect to a SSH server it's like my input is only sent once every second. If I hold a key, it doesn't print anything for a second and after that second I see every keystroke I did during that time.
This is how it looks on the working servers:
This is how it looks on the ones with the issue:
Things I have tested/found out
- Changing the "UseDNS" setting in /etc/sshd doesn't fix it
- It happens with bash (and zsh) on Debian (OpenSSH_7.4p1 Debian-10+deb9u6, OpenSSL 1.0.2r 26 Feb 2019) and Ash on Alpine Linux (OpenSSH_7.9p1, OpenSSL 1.1.1b 26 Feb 2019)
- It doesn't happen on Alpine Linux OpenSSH_7.7p1, LibreSSL 2.7.4
- It doesn't happen with every machine, just some (not depending on the distro)
- resolv.conf is correct
- Error happens with and without ClientAliveInterval (tested on client and server)
- Pinging the devices is always fast (less than 1 ms) so it's only SSH
- It also lags when I ssh from the linux subsystem on Windows 10 and with Putty and with MobaXterm
- No problems when I connect from Linux instead of Windows
Does anyone have any clues or things I could try?
Thanks
linux ssh windows-10 putty lag
asked Apr 4 at 19:32
ChristianChristian
116417
I've had a strange problem with SSH connections inside my LAN for a few months. It only happens when I'm using my Windows 10 device to connect to a (barebone) linux machine.
When I connect to a SSH server it's like my input is only sent once every second. If I hold a key, it doesn't print anything for a second and after that second I see every keystroke I did during that time.
This is how it looks on the working servers:
This is how it looks on the ones with the issue:
Things I have tested/found out
- Changing the "UseDNS" setting in /etc/sshd doesn't fix it
- It happens with bash (and zsh) on Debian (OpenSSH_7.4p1 Debian-10+deb9u6, OpenSSL 1.0.2r 26 Feb 2019) and Ash on Alpine Linux (OpenSSH_7.9p1, OpenSSL 1.1.1b 26 Feb 2019)
- It doesn't happen on Alpine Linux OpenSSH_7.7p1, LibreSSL 2.7.4
- It doesn't happen with every machine, just some (not depending on the distro)
- resolv.conf is correct
- Error happens with and without ClientAliveInterval (tested on client and server)
- Pinging the devices is always fast (less than 1 ms) so it's only SSH
- It also lags when I ssh from the linux subsystem on Windows 10 and with Putty and with MobaXterm
- No problems when I connect from Linux instead of Windows
Does anyone have any clues or things I could try?
Thanks
linux ssh windows-10 putty lag
linux ssh windows-10 putty lag
asked Apr 4 at 19:32
ChristianChristian
116417
asked Apr 4 at 19:32
ChristianChristian
116417
asked Apr 4 at 19:32
ChristianChristian
116417
asked Apr 4 at 19:32
ChristianChristian
116417
asked Apr 4 at 19:32
ChristianChristian
116417
116417
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Typically this is a sign of Nagle's algorithm, you can turn that socket option off.
(I have seen similar TCP delays between Linux and Windows before in other cases as well. In one case it was caused by interactions between TCP Windows sizes and PSH (Push) flags which caused Windows to acknowledge late and/or retry.)
edited Apr 5 at 5:45
Solomon Ucko
1054
answered Apr 4 at 19:45
eckeseckes
746617
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f961576%2fssh-lag-in-lan-on-some-machines-mixed-distros%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Typically this is a sign of Nagle's algorithm, you can turn that socket option off.
(I have seen similar TCP delays between Linux and Windows before in other cases as well. In one case it was caused by interactions between TCP Windows sizes and PSH (Push) flags which caused Windows to acknowledge late and/or retry.)
edited Apr 5 at 5:45
Solomon Ucko
1054
answered Apr 4 at 19:45
eckeseckes
746617
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
add a comment |
Typically this is a sign of Nagle's algorithm, you can turn that socket option off.
(I have seen similar TCP delays between Linux and Windows before in other cases as well. In one case it was caused by interactions between TCP Windows sizes and PSH (Push) flags which caused Windows to acknowledge late and/or retry.)
edited Apr 5 at 5:45
Solomon Ucko
1054
answered Apr 4 at 19:45
eckeseckes
746617
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
add a comment |
Typically this is a sign of Nagle's algorithm, you can turn that socket option off.
(I have seen similar TCP delays between Linux and Windows before in other cases as well. In one case it was caused by interactions between TCP Windows sizes and PSH (Push) flags which caused Windows to acknowledge late and/or retry.)
edited Apr 5 at 5:45
Solomon Ucko
1054
answered Apr 4 at 19:45
eckeseckes
746617
Typically this is a sign of Nagle's algorithm, you can turn that socket option off.
(I have seen similar TCP delays between Linux and Windows before in other cases as well. In one case it was caused by interactions between TCP Windows sizes and PSH (Push) flags which caused Windows to acknowledge late and/or retry.)
edited Apr 5 at 5:45
Solomon Ucko
1054
answered Apr 4 at 19:45
eckeseckes
746617
edited Apr 5 at 5:45
Solomon Ucko
1054
edited Apr 5 at 5:45
Solomon Ucko
1054
edited Apr 5 at 5:45
Solomon Ucko
1054
1054
answered Apr 4 at 19:45
eckeseckes
746617
answered Apr 4 at 19:45
eckeseckes
746617
answered Apr 4 at 19:45
eckeseckes
746617
746617
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
add a comment |
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
Awesome, thanks for that quick fix! In the Putty settings I unchecked the "Disable Nagle's algorithm" checkbox (which seems to be ticked by default) and now it works!
– Christian
Apr 4 at 19:49
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian thanks for confirmation, I simplified my answer a bit
– eckes
Apr 4 at 20:04
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@Christian, I am confused. You enabled Nagle's algortihm, and now the characters do not come in larger packets? That seems the wrong way around to me, so maybe the answer before the edit was actually better.
– Carsten S
Apr 5 at 9:22
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
@CarstenS yes all I did was uncheck the "disable Nagle's algorithm" in Putty meaning I enabled it. But I think it's an older version of Putty so maybe the lable on the checkbox is wrong
– Christian
Apr 5 at 12:47
Hm, indeed strange.
– eckes
Apr 5 at 17:12
Hm, indeed strange.
– eckes
Apr 5 at 17:12
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f961576%2fssh-lag-in-lan-on-some-machines-mixed-distros%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
