Public bug reported: NetworkManager keyfiles allows to specify "scope: link" routes, by leaving the gateway/next_hop field unspecified, e.g.:
route3=2.2.2.2/7 route4=3.3.3.3/6,0.0.0.0,4 route3=4:5:6:7:8:9:0:1/63,::,5 To keep compatibility, netplan needs to be able to accept "scope: link" routes for the NM backend and render the keyfile accordingly. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Impish) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949761 Title: NM backend does not accept "scope: link" routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1949761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs