>From what I can tell, the routing is exactly how it should be:
[from the bug description] root@search-3 /run/systemd/network # ip route default via 95.216.96.129 dev enp0s31f6 proto static 10.0.0.0/24 dev tun0 proto kernel scope link src 10.0.0.13 10.0.2.0/24 dev vlan4000 proto kernel scope link src 10.0.2.3 95.216.96.128/26 dev enp0s31f6 proto kernel scope link src 95.216.96.148 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-c7cc901345e8 proto kernel scope link src 172.18.0.1 """ its missing to add 95.216.96.128/26 via 95.216.96.129 dev enp0s31f6 """ It's actually not missing a route -- the IP is defined as being 95.216.96.148/26; which means that it's on the same subnet as 95.216.96.129 (your gateway) already (/26 for this address is from 95.216.96.128 (the network address) to 95.216.96.191. The additional route is simply superfluous, it should not be required. networkd or the kernel may be ignoring them since the routes are already existing. Could you please tell us more about what you are trying to achieve? Are you trying to ping something that isn't responding the way you expect? Is some system not reachable? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826459 Title: systemd-networkd not installing GatewayOnlink=true To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1826459/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
