Description of problem: After upgrading to F24 my journal was getting spammed with messages like this every second: Jun 10 10:11:26 host.example.com systemd-networkd[1203]: enp5s0: Starting DHCPv6 client on NDisc request failed: Invalid argument Interface enp5s0 is joined to a bridge - it's network file looks like this: [Match] MACAddress=aa:bb:cc:dd:ee:ff [Network] Bridge=br0 It is connected to a network where the IPv6 RAs say that DHCPv6 should be used, so is starting DHCPv6 on the interface, even though it is joined to a bridge but that then fails because of the bridge presumably. Adding IPv6AcceptRouterAdvertisements=false to make it ignore the RAs on that interface seems to fix things but maybe that should be implied when an interface is joined to a bridge? Version-Release number of selected component (if applicable): systemd-229-8.fc24.x86_64
It's fixed upstream in https://github.com/systemd/systemd/commit/2b00a4e03d. We probably should backport this. Seems easy enough.
systemd-229-11.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-10e709e870
systemd-229-11.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-10e709e870
systemd-229-12.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-10e709e870
systemd-229-12.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-10e709e870
systemd-229-12.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.