Some package (between 4.3.3-459 -> 4.3.3-466) update broke dhcp server



yesterday one of these updates seems to have broken dhcp server so older Win client PCs w/ Win7 (Win10 seems to be more resilient if there is no DHCP answer) couldn’t connect w/ failure ’ Unidentified Network and No network Access

From ~log/apt/history.log:

Start-Date: 2019-04-02  16:47:23
Commandline: apt-get -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-overwrite -o DPkg::Options::=--force-overwrite-dir --trivial-only=no --assume-yes --quiet=1 -u dist-upgrade
Upgrade: univention-directory-notifier:amd64 (12.0.1-11A~, 12.0.1-12A~, ntfs-3g:amd64 (1:2016.2.22AR.1+dfsg-1, 1:2016.2.22AR.1+dfsg-1+deb9u1), libntfs-3g871:amd64 (1:2016.2.22AR.1+dfsg-1, 1:2016.2.22
AR.1+dfsg-1+deb9u1), univention-base-files:amd64 (7.0.0-20A~, 7.0.0-21A~, univention-errata-level:amd64 (4.3.3-459, 4.3.3-466), firefox-esr-l10n-de:amd64 (60.5.1esr-1~deb9u1, 60.6.1esr-1~deb9u1), uni
vention-base-packages:amd64 (7.0.0-20A~, 7.0.0-21A~, univention-pam:amd64 (11.0.1-4A~, 11.0.1-5A~, firefox-esr:amd64 (60.5.1esr-1~deb9u1, 60.6.1esr-1~deb9u1)
End-Date: 2019-04-02 16:49:13

At ~log/syslog we see:

Apr  2 16:48:21 metis dhcpd[26172]: receive_packet failed on br0: Network is down

and from this time until we restart DHCP w/ systemctl restart univention-dhcp.service there seems to be no more DHCP response.

Maybe something is buggy?

Regards Robert



as you have configured a bridged network (therefore the message of br0) I would say your system is back to a single NIC (eth0 or so) while all services try to access br0.

Reconfigure your network.