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 (for nfs), and a similar client with also two interfaces, one with an address at

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:




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


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 (, 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?

  • 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

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.