** Summary changed: - netplan ignores NetworkManager ipv4.route-metric + [SRU] Backport netplan.io 1.1.0-1ubuntu2 to 24.04
** Description changed: - I have previously created the ticket - https://bugs.launchpad.net/netplan/+bug/2076172 which was solved with - this MR: https://github.com/canonical/netplan/pull/495 and eventually it - was released. + [ Impact ] - The issue was initially identified on Ubuntu 24.04 and it's affecting - users of the Proton VPN app. We have a temporary workaround for it but - we'd like to have this backported to Ubuntu 24.04 as soon as possible, - as I was informed that a full backported might be done towards the end - of the year. + Dummy connections are not being passed the ipv4.route-metric value from + NM, instead they have the default value of 550, though this behavior was + not observed with the IPv6 protocol. + + This has been fixed in + https://blog.slyon.de/2024/08/14/netplan-v1-1-released/, which was + initially reported here. + + [ Test Plan ] + + On Ubuntu 24.04: + + 1) Create dummy connection via nmcli: nmcli c a type dummy ifname + pvpnksintrf0 con-name pvpn-killswitch ipv4.method manual ipv4.addresses + "100.85.0.1/24" ipv4.gateway "100.85.0.1" ipv6.method manual + ipv6.addresses "fdeb:446c:912d:08da::/64" ipv6.gateway + "fdeb:446c:912d:08da::1" ipv4.route-metric 98 ipv6.route-metric 95 + + 2) Run the command to show connection info: nmcli c s pvpn-killswitch + + 2.1) Notice that ipv6.route-metric has been taken but not ipv4.route- + metric, even though the data is present under /etc/netplan/90*.yml + + [ Where problems could occur ] + + + [ Other Info ] ** Description changed: [ Impact ] Dummy connections are not being passed the ipv4.route-metric value from NM, instead they have the default value of 550, though this behavior was not observed with the IPv6 protocol. This has been fixed in https://blog.slyon.de/2024/08/14/netplan-v1-1-released/, which was - initially reported here. + initially reported here: + https://bugs.launchpad.net/netplan/+bug/2076172. [ Test Plan ] On Ubuntu 24.04: 1) Create dummy connection via nmcli: nmcli c a type dummy ifname pvpnksintrf0 con-name pvpn-killswitch ipv4.method manual ipv4.addresses "100.85.0.1/24" ipv4.gateway "100.85.0.1" ipv6.method manual ipv6.addresses "fdeb:446c:912d:08da::/64" ipv6.gateway "fdeb:446c:912d:08da::1" ipv4.route-metric 98 ipv6.route-metric 95 2) Run the command to show connection info: nmcli c s pvpn-killswitch 2.1) Notice that ipv6.route-metric has been taken but not ipv4.route- metric, even though the data is present under /etc/netplan/90*.yml [ Where problems could occur ] - [ Other Info ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077011 Title: [SRU] Backport netplan.io 1.1.0-1ubuntu2 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
