Destination Host Unreachable on Ubuntu Netplan, same subnet, same routes












1















I've been banging my head against this problem for days and can't find a solution.



I have a network with a server with two interfaces, one for normal traffic and one with an address 10.72.0.23/12 (for nfs), and a similar client with also two interfaces, one with an address at 10.76.0.17/12.



I've tried about a billion iterations of the netplan options, but at the core I'm constantly stalled by the fact that these two interfaces refuse to connect to each other in this configuration.



If I configure interfaces like so, they connect:



server: 10.72.0.23/12
client: 10.72.0.17/12


or



server: 10.76.0.23/12
client: 10.76.0.17/12


But if I set them up like this, they refuse to communicate (Destination host unreachable):



server: 10.72.0.23/12
client: 10.76.0.17/12


Sadly, for my purposes, I'm unable to configure them the first way permanently - the client and server addresses need to have more than 255 available IPs. These addresses are supposed to connect as they have the same subnet (10.64.0.0/12), yet they do not do so.



There's no firewall. There's no ip conflict. They're on the same subnet. They have the same routes configured. Since they can connect when they have the same first two octets, I know the hardware is working. Everything stops dead the moment I give them the IPs above (or nearby ones).



Is this a bug, or is there some undocumented feature of linux routing at play here?










share|improve this question























  • Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

    – slangasek
    Jan 13 at 1:17











  • (the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

    – slangasek
    Jan 13 at 6:36
















1















I've been banging my head against this problem for days and can't find a solution.



I have a network with a server with two interfaces, one for normal traffic and one with an address 10.72.0.23/12 (for nfs), and a similar client with also two interfaces, one with an address at 10.76.0.17/12.



I've tried about a billion iterations of the netplan options, but at the core I'm constantly stalled by the fact that these two interfaces refuse to connect to each other in this configuration.



If I configure interfaces like so, they connect:



server: 10.72.0.23/12
client: 10.72.0.17/12


or



server: 10.76.0.23/12
client: 10.76.0.17/12


But if I set them up like this, they refuse to communicate (Destination host unreachable):



server: 10.72.0.23/12
client: 10.76.0.17/12


Sadly, for my purposes, I'm unable to configure them the first way permanently - the client and server addresses need to have more than 255 available IPs. These addresses are supposed to connect as they have the same subnet (10.64.0.0/12), yet they do not do so.



There's no firewall. There's no ip conflict. They're on the same subnet. They have the same routes configured. Since they can connect when they have the same first two octets, I know the hardware is working. Everything stops dead the moment I give them the IPs above (or nearby ones).



Is this a bug, or is there some undocumented feature of linux routing at play here?










share|improve this question























  • Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

    – slangasek
    Jan 13 at 1:17











  • (the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

    – slangasek
    Jan 13 at 6:36














1












1








1








I've been banging my head against this problem for days and can't find a solution.



I have a network with a server with two interfaces, one for normal traffic and one with an address 10.72.0.23/12 (for nfs), and a similar client with also two interfaces, one with an address at 10.76.0.17/12.



I've tried about a billion iterations of the netplan options, but at the core I'm constantly stalled by the fact that these two interfaces refuse to connect to each other in this configuration.



If I configure interfaces like so, they connect:



server: 10.72.0.23/12
client: 10.72.0.17/12


or



server: 10.76.0.23/12
client: 10.76.0.17/12


But if I set them up like this, they refuse to communicate (Destination host unreachable):



server: 10.72.0.23/12
client: 10.76.0.17/12


Sadly, for my purposes, I'm unable to configure them the first way permanently - the client and server addresses need to have more than 255 available IPs. These addresses are supposed to connect as they have the same subnet (10.64.0.0/12), yet they do not do so.



There's no firewall. There's no ip conflict. They're on the same subnet. They have the same routes configured. Since they can connect when they have the same first two octets, I know the hardware is working. Everything stops dead the moment I give them the IPs above (or nearby ones).



Is this a bug, or is there some undocumented feature of linux routing at play here?










share|improve this question














I've been banging my head against this problem for days and can't find a solution.



I have a network with a server with two interfaces, one for normal traffic and one with an address 10.72.0.23/12 (for nfs), and a similar client with also two interfaces, one with an address at 10.76.0.17/12.



I've tried about a billion iterations of the netplan options, but at the core I'm constantly stalled by the fact that these two interfaces refuse to connect to each other in this configuration.



If I configure interfaces like so, they connect:



server: 10.72.0.23/12
client: 10.72.0.17/12


or



server: 10.76.0.23/12
client: 10.76.0.17/12


But if I set them up like this, they refuse to communicate (Destination host unreachable):



server: 10.72.0.23/12
client: 10.76.0.17/12


Sadly, for my purposes, I'm unable to configure them the first way permanently - the client and server addresses need to have more than 255 available IPs. These addresses are supposed to connect as they have the same subnet (10.64.0.0/12), yet they do not do so.



There's no firewall. There's no ip conflict. They're on the same subnet. They have the same routes configured. Since they can connect when they have the same first two octets, I know the hardware is working. Everything stops dead the moment I give them the IPs above (or nearby ones).



Is this a bug, or is there some undocumented feature of linux routing at play here?







networking netplan systemd-networkd






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 12 at 1:22









Aaron ThomasAaron Thomas

61




61













  • Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

    – slangasek
    Jan 13 at 1:17











  • (the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

    – slangasek
    Jan 13 at 6:36



















  • Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

    – slangasek
    Jan 13 at 1:17











  • (the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

    – slangasek
    Jan 13 at 6:36

















Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

– slangasek
Jan 13 at 1:17





Which Ubuntu release, and which versions of the netplan.io and systemd packages are installed? What are the netmasks on the interfaces as shown by 'ip addr show'?

– slangasek
Jan 13 at 1:17













(the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

– slangasek
Jan 13 at 6:36





(the reason for this question is I believe there was a bug that caused /24 netmasks to be used unconditionally, but that this bug has been fixed in latest versions of the packages)

– slangasek
Jan 13 at 6:36










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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1109029%2fdestination-host-unreachable-on-ubuntu-netplan-same-subnet-same-routes%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
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1109029%2fdestination-host-unreachable-on-ubuntu-netplan-same-subnet-same-routes%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

張江高科駅