Cannot ping certain IP
I have a virtual machine with Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64). From this machine I need to access some third-party API. They don't even have a domain name, so access is by IP only. The API is reachable, I can access it from my dev machine, and various online services can ping its IP too.
From my virtual machine I'm not able to ping this IP however. Everyhting else except this IP works fine, I can ping other IPs no problem. My hosting provider (Hetzner) says that from their side everything looks fine. Is there anything I can do to make this IP reachable?
networking
add a comment |
I have a virtual machine with Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64). From this machine I need to access some third-party API. They don't even have a domain name, so access is by IP only. The API is reachable, I can access it from my dev machine, and various online services can ping its IP too.
From my virtual machine I'm not able to ping this IP however. Everyhting else except this IP works fine, I can ping other IPs no problem. My hosting provider (Hetzner) says that from their side everything looks fine. Is there anything I can do to make this IP reachable?
networking
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
1
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30
add a comment |
I have a virtual machine with Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64). From this machine I need to access some third-party API. They don't even have a domain name, so access is by IP only. The API is reachable, I can access it from my dev machine, and various online services can ping its IP too.
From my virtual machine I'm not able to ping this IP however. Everyhting else except this IP works fine, I can ping other IPs no problem. My hosting provider (Hetzner) says that from their side everything looks fine. Is there anything I can do to make this IP reachable?
networking
I have a virtual machine with Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64). From this machine I need to access some third-party API. They don't even have a domain name, so access is by IP only. The API is reachable, I can access it from my dev machine, and various online services can ping its IP too.
From my virtual machine I'm not able to ping this IP however. Everyhting else except this IP works fine, I can ping other IPs no problem. My hosting provider (Hetzner) says that from their side everything looks fine. Is there anything I can do to make this IP reachable?
networking
networking
edited Feb 11 at 13:30
Konstantin Kuznetsov
asked Feb 11 at 12:54
Konstantin KuznetsovKonstantin Kuznetsov
1011
1011
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
1
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30
add a comment |
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
1
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
1
1
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1117361%2fcannot-ping-certain-ip%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 Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1117361%2fcannot-ping-certain-ip%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
are you able to ping other ip's instead? if not, you might be blocking outgoing icmp traffic perhaps.
– AlexOnLinux
Feb 11 at 13:23
I edited my post. Everything else works fine, I can ping other IPs without any problems.
– Konstantin Kuznetsov
Feb 11 at 13:31
1
Firstly update your machine (16.04.5 was released in 2-August-2018, so your vm is at least that out-of-date), but confirm you can ping those other IPs from the VM itself. It sounds like a problem with your HOST restricting traffic (if not the fact that your system is just months behind with updates).
– guiverc
Feb 11 at 13:39
I upgraded to latest 16.04, and on the other machine I even upgraded from 16.04 to 18.04. Cannot ping this IP from both of them. Any other IP pings just fine, there's backend running which talks to external APIs a lot. I also created blank new 18.04 VM in same data center and from it I can ping this IP. How can I check if my host restricting traffic to this ip?
– Konstantin Kuznetsov
Feb 11 at 17:30