Bug#779571: systemd: stop v4 dhcpclient when the carrier is lost

Christos Trochalakis yatiohi at ideopolis.gr
Mon Mar 2 14:50:58 GMT 2015


Package: systemd
Version: 215-12
Severity: important

The check for a running v4 dhcp client is using DHCP_SUPPORT_V6
flag instead of DHCP_SUPPORT_V4.

As a result, when the carrier was lost, systemd was not cleaning up the
relevant addresses and routes. If the carrier was regained in another
environment, with a different subnet and gateway, the system would end
up with multiple addresses and default gateways and thus a broken
network configuration.

This bug was introduced in v215 (ed942a9e), and was fixed from v216 as a
side effect of ba179154. The attached patch fixes that until debian
moves to the latest systemd version.

The above scenario happened quite regularly on my laptop when switching
locations. For the record, I am using systemd-networkd.service and
wpa_supplicant at wlan0.service handling authentication.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-networkd-link-fix-stopping-v4-dhcpclient-when-the-ca.patch
Type: text/x-diff
Size: 1358 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150302/bac785d0/attachment.patch>


More information about the Pkg-systemd-maintainers mailing list