> whereas in truth the combination of https://github.com/systemd/systemd/pull/17535 and its networkd counterpart did not resolve it.
This statement is most probably not correct: what I meant is that the changes made upstream did not resolve our issue. Because the issue was fixed upstream a few months ago, I was under the assumption that we were running a version of systemd that included the fixes, which is clearly not the case: I realized that after Yu Watanabe mentioned a discrepancy between the versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891215 Title: systemd-resolved re-creates /run/systemd/resolve/*resolv.conf for every IPv6 RA received To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1891215/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
