I've tested netplan.io 0.103-0ubuntu5~20.04.3 from focal-proposed.
The netplan generator command was run successfully, producing correct "scope: link" routes with empty gateway/next_hop:
root@sru-ff:~# dpkg -l | grep netplan ii libnetplan0:amd64 0.103-0ubuntu5~20.04.3 amd64 YAML network configuration abstraction runtime library ii netplan.io 0.103-0ubuntu5~20.04.3 amd64 YAML network configuration abstraction for various backends
root@sru-ff:~# mkdir -p tmp/etc/netplan root@sru-ff:~# vim tmp/etc/netplan/test.yaml root@sru-ff:~# cat tmp/etc/netplan/test.yaml network: renderer: NetworkManager ethernets: eth0: addresses: [1.2.3.4/24, fe20::3/16] routes: - to: 2.2.2.2/7 scope: link - to: 3.3.3.3/6 scope: link metric: 4 - to: 4:5:6:7:8:9:0:1/63 scope: link metric: 5 root@sru-ff:~# /usr/lib/netplan/generate -r tmp/ root@sru-ff:~# cat tmp/run/NetworkManager/system-connections/netplan-eth0.nmconnection | grep "route.=" route1=2.2.2.2/7 route2=3.3.3.3/6,,4 route1=4:5:6:7:8:9:0:1/63,,5
I've tested netplan.io 0.103-0ubuntu5~ 20.04.3 from focal-proposed.
The netplan generator command was run successfully, producing correct "scope: link" routes with empty gateway/next_hop:
root@sru-ff:~# dpkg -l | grep netplan 20.04.3 amd64 YAML network configuration abstraction runtime library 20.04.3 amd64 YAML network configuration abstraction for various backends
ii libnetplan0:amd64 0.103-0ubuntu5~
ii netplan.io 0.103-0ubuntu5~
root@sru-ff:~# mkdir -p tmp/etc/netplan netplan/ test.yaml netplan/ test.yaml netplan/ generate -r tmp/ NetworkManager/ system- connections/ netplan- eth0.nmconnecti on | grep "route.=" 4:5:6:7: 8:9:0:1/ 63,,5
root@sru-ff:~# vim tmp/etc/
root@sru-ff:~# cat tmp/etc/
network:
renderer: NetworkManager
ethernets:
eth0:
addresses: [1.2.3.4/24, fe20::3/16]
routes:
- to: 2.2.2.2/7
scope: link
- to: 3.3.3.3/6
scope: link
metric: 4
- to: 4:5:6:7:8:9:0:1/63
scope: link
metric: 5
root@sru-ff:~# /usr/lib/
root@sru-ff:~# cat tmp/run/
route1=2.2.2.2/7
route2=3.3.3.3/6,,4
route1=