I see a huge flood in journalctl from NM, which is probably caused by tons of RA announcements. Aug 10 10:55:28 testsethostname dnsmasq-dhcp[18631]: RTR-ADVERT(simbr) 2620:52:0:1086:: Aug 10 10:55:28 testsethostname NetworkManager[21459]: <debug> [1565448928.5546] ndisc-lndp[0x55cae74930e0,"eth0"]: processing libndp events Aug 10 10:55:28 testsethostname dnsmasq-dhcp[18631]: RTR-ADVERT(simbr) 2620:52:0:1086:: Aug 10 10:55:28 testsethostname NetworkManager[21459]: <debug> [1565448928.5548] ndisc-lndp[0x55cae74930e0,"eth0"]: processing libndp events Aug 10 10:55:28 testsethostname dnsmasq-dhcp[18631]: RTR-ADVERT(simbr) 2620:52:0:1086:: Aug 10 10:55:28 testsethostname NetworkManager[21459]: <debug> [1565448928.5551] ndisc-lndp[0x55cae74930e0,"eth0"]: processing libndp events Aug 10 10:55:28 testsethostname dnsmasq-dhcp[18631]: RTR-ADVERT(simbr) 2620:52:0:1086:: Aug 10 10:55:28 testsethostname NetworkManager[21459]: <debug> [1565448928.5553] ndisc-lndp[0x55cae74930e0,"eth0"]: processing libndp events simbr is configured in virtual setup environment used for NetworkManager's tests. # Create the 'simbr' - providing both 10.x ipv4 and 2620:52:0 ipv6 dhcp ip netns exec vethsetup ip link add name simbr type bridge forward_delay 0 stp_state 1 ip netns exec vethsetup ip link set simbr up ip netns exec vethsetup ip addr add 10.16.1.1/24 dev simbr ip netns exec vethsetup ip -6 addr add 2620:52:0:1086::1/64 dev simbr # Add eth10 peer into the simbr ip netns exec vethsetup ip link set eth10p master simbr # Run joint DHCP4/DHCP6 server with router advertisement enabled in veth namespace ip netns exec vethsetup dnsmasq --pid-file=/tmp/dhcp_simbr.pid --dhcp-leasefile=/tmp/dhcp_simbr.lease --dhcp-range=10.16.1.10,10.16.1.254,240 --dhcp-range=2620:52:0:1086::10,2620:52:0:1086::1ff,slaac,64,240 --enable-ra --interface=simbr --bind-interfaces
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
Confirming bug, it is in upstream. Created restartable reproducer [1]. Reliably reports many packets on v2.80, but v2.79 is ok. Vanilla build from upstream is affected too. 1. https://github.com/InfrastructureServices/dnsmasq-tests/blob/master/bz1739797.sh
Found breaking commit to be [1]. It seems to be intention to send it fast, but maybe damage created was not well considered. Impact is significant. 1. http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=0a496f059c1e9d75c33cce4c1211d58422ba4f62
Sent information upstream, for now without any patch. http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q3/013255.html
FEDORA-2019-7f297cb49a has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f297cb49a
FEDORA-2019-883c54f9e9 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-883c54f9e9
dnsmasq-2.80-10.fc30 has been pushed to the Fedora 30 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-2019-7f297cb49a
dnsmasq-2.80-10.fc31 has been pushed to the Fedora 31 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-2019-883c54f9e9
dnsmasq-2.80-10.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
dnsmasq-2.80-10.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.