[Bug 1949761] Re: NM backend does not accept "scope: link" routes

This bug was fixed in the package netplan.io - 0.103-0ubuntu9 --- netplan.io (0.103-0ubuntu9) jammy; urgency=medium [ Lukas Märdian ] * Add an upstream patch for glib 2.70 compatibility * Add d/p/0010-parse-nm-Handle-missing-gateway-in-keyfile-routes-ke.patch (LP: #1949761)

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

This bug was fixed in the package netplan.io - 0.103-0ubuntu5~21.04.3 --- netplan.io (0.103-0ubuntu5~21.04.3) hirsute; urgency=medium [ Nicolas Bock ] * d/p/0001-Add-support-for-additional-Link-options-225-LP-17717.patch: - Add offload configuration options. (LP: #177174

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

This bug was fixed in the package netplan.io - 0.103-0ubuntu5~20.04.3 --- netplan.io (0.103-0ubuntu5~20.04.3) focal; urgency=medium [ Nicolas Bock ] * d/p/0001-Add-support-for-additional-Link-options-225-LP-17717.patch: - Add offload configuration options. (LP: #1771740)

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

This bug was fixed in the package netplan.io - 0.103-0ubuntu7.1 --- netplan.io (0.103-0ubuntu7.1) impish; urgency=medium [ Nicolas Bock ] * d/p/0001-Add-support-for-additional-Link-options-225-LP-17717.patch: - Add offload configuration options. (LP: #1771740) * Add d/

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

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 configura

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

I've tested netplan.io 0.103-0ubuntu5~21.04.3 from hirsute-proposed. The netplan generator command was run successfully, producing correct "scope: link" routes with empty gateway/next_hop: root@sru-hh:~# dpkg -l | grep netplan ii libnetplan0:amd64 0.103-0ubuntu5~21.04.3 amd64 YAML network configu

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

I've tested netplan.io 0.103-0ubuntu7.1 from impish-proposed and attached the autopkgtest logs to the bug description, according to https://wiki.ubuntu.com/NetplanUpdates. The netplan generator command was run successfully, producing correct "scope: link" routes with empty gateway/next_hop: root@

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

** Description changed: [Impact] The NetworkManager snap (using the libnetplan YAML backend) makes use of the "link" routing scope in certain situations, which is represented by an empty or unspecified gateway/next_hop field in the keyfile definition (e.g. "route3=2.2.2.2/7", "route4=3.

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

Hello Lukas, or anyone else affected, Accepted netplan.io into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.103-0ubuntu5~21.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

Hello Lukas, or anyone else affected, Accepted netplan.io into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.103-0ubuntu5~20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. S

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

** Changed in: netplan.io (Ubuntu Jammy) Status: New => Fix Committed -- 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 n

[Bug 1949761] Re: NM backend does not accept "scope: link" routes

** Description changed: + [Impact] + The NetworkManager snap (using the libnetplan YAML backend) makes use of the + "link" routing scope in certain situations, which is represented by an empty or + unspecified gateway/next_hop field in the keyfile definition (e.g. + "route3=2.2.2.2/7", "route4=3.