SSH connection timed out / high packet loss
I have difficulties to connect to my SSH server from one particular location. I know the server is running. Sometimes, I can even connect to the server from the location. However, five minutes later, it is not working anymore.
I can traceroute to the server, but there are usually quite a few packets "not acknowledged within the expected timeout" at the end of the route. When I try to ping the IP address, there is usually very high packet loss (sometimes 100%). Ping of other addresses works fine. Moreover, While ping gives 80-100% packet loss, ping -f gives as low as 1% packet loss at the same time.
The server and the location I want to connect from are in different countries. The SSH connection works fine from other locations. One other location tested in the same city worked fine.
The server is sitting on ipv4 only, the network I want to connect from has both ipv4 and ipv6. I had no luck with ssh -4.
ssh -vvv gives no more information than:
Connection timed out
Another server (not managed by me, sitting on the same network as mine) has the same symptoms.
All servers and stations are debian machines.
Is there something I can try? I am unsure where to look to resolve this issue.
I am aware of packet loss and unable to ssh
question. However, there was no answer and it was much less specific.
networking ssh ping
asked Jan 29 at 11:31
falesfales
134
add a comment |
I have difficulties to connect to my SSH server from one particular location. I know the server is running. Sometimes, I can even connect to the server from the location. However, five minutes later, it is not working anymore.
I can traceroute to the server, but there are usually quite a few packets "not acknowledged within the expected timeout" at the end of the route. When I try to ping the IP address, there is usually very high packet loss (sometimes 100%). Ping of other addresses works fine. Moreover, While ping gives 80-100% packet loss, ping -f gives as low as 1% packet loss at the same time.
The server and the location I want to connect from are in different countries. The SSH connection works fine from other locations. One other location tested in the same city worked fine.
The server is sitting on ipv4 only, the network I want to connect from has both ipv4 and ipv6. I had no luck with ssh -4.
ssh -vvv gives no more information than:
Connection timed out
Another server (not managed by me, sitting on the same network as mine) has the same symptoms.
All servers and stations are debian machines.
Is there something I can try? I am unsure where to look to resolve this issue.
I am aware of packet loss and unable to ssh
question. However, there was no answer and it was much less specific.
networking ssh ping
asked Jan 29 at 11:31
falesfales
134
add a comment |
I have difficulties to connect to my SSH server from one particular location. I know the server is running. Sometimes, I can even connect to the server from the location. However, five minutes later, it is not working anymore.
I can traceroute to the server, but there are usually quite a few packets "not acknowledged within the expected timeout" at the end of the route. When I try to ping the IP address, there is usually very high packet loss (sometimes 100%). Ping of other addresses works fine. Moreover, While ping gives 80-100% packet loss, ping -f gives as low as 1% packet loss at the same time.
The server and the location I want to connect from are in different countries. The SSH connection works fine from other locations. One other location tested in the same city worked fine.
The server is sitting on ipv4 only, the network I want to connect from has both ipv4 and ipv6. I had no luck with ssh -4.
ssh -vvv gives no more information than:
Connection timed out
Another server (not managed by me, sitting on the same network as mine) has the same symptoms.
All servers and stations are debian machines.
Is there something I can try? I am unsure where to look to resolve this issue.
I am aware of packet loss and unable to ssh
question. However, there was no answer and it was much less specific.
networking ssh ping
asked Jan 29 at 11:31
falesfales
134
I have difficulties to connect to my SSH server from one particular location. I know the server is running. Sometimes, I can even connect to the server from the location. However, five minutes later, it is not working anymore.
I can traceroute to the server, but there are usually quite a few packets "not acknowledged within the expected timeout" at the end of the route. When I try to ping the IP address, there is usually very high packet loss (sometimes 100%). Ping of other addresses works fine. Moreover, While ping gives 80-100% packet loss, ping -f gives as low as 1% packet loss at the same time.
The server and the location I want to connect from are in different countries. The SSH connection works fine from other locations. One other location tested in the same city worked fine.
The server is sitting on ipv4 only, the network I want to connect from has both ipv4 and ipv6. I had no luck with ssh -4.
ssh -vvv gives no more information than:
Connection timed out
Another server (not managed by me, sitting on the same network as mine) has the same symptoms.
All servers and stations are debian machines.
Is there something I can try? I am unsure where to look to resolve this issue.
I am aware of packet loss and unable to ssh
question. However, there was no answer and it was much less specific.
networking ssh ping
networking ssh ping
asked Jan 29 at 11:31
falesfales
134
asked Jan 29 at 11:31
falesfales
134
asked Jan 29 at 11:31
falesfales
134
asked Jan 29 at 11:31
falesfales
134
asked Jan 29 at 11:31
falesfales
134
134
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1399607%2fssh-connection-timed-out-high-packet-loss%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1399607%2fssh-connection-timed-out-high-packet-loss%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
