** Description changed: + [impact] + + routing policy rules not correctly configured + + [test case] + + more detail in upstream bug linked from original description. + + configure interface with: + + [Match] + Name = ens3 + + [Network] + Address = 10.0.0.1/32 + + [RoutingPolicyRule] + Family = both + IncomingInterface = ens3 + Table = 42 + Priority = 42 + + + then networkctl reload. then update the network file with: + + [Route] + Table = 42 + Destination = 10.0.0.0/24 + Gateway = 0.0.0.0 + + and run networkctl reload again, checking systemd-networkd for error. + + [regression potential] + + failure to properly configure networking in general, or policy routes. + + [scope] + + this is needed only for h. + + this is fixed already in i, and this is not reproducable in g. + + see original descrption for link to specific upstream issue and pr. + + [original description] + The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
