Package: dhcpcd5
Version: 6.0.5-2
Severity: normal
Hi,
this box has its network interface configured statically in
/etc/network/interfaces. dhcpcd5 is installed but should not be active
at this time. (I would have liked to use DHCP, but neither dhcpcd5 nor
isc-dhcp-client work properly on a machine that only wakes once per
day for a few minutes and usessystemd. Also I sometimes use a wireless
dongle and that needs DHCP.)
Anyway, last night the box woke up and ...
Apr 05 02:00:30 mrmackey kernel: Restarting tasks ... done.
Apr 05 02:00:30 mrmackey dhcpcd[622]: eth0: carrier lost
Apr 05 02:00:30 mrmackey dhcpcd[622]: eth0: deleting host route to 192.168.0.25
via 127.0.0.1
Apr 05 02:00:30 mrmackey dhcpcd[622]: eth0: deleting route to 192.168.0.0/24
Apr 05 02:00:30 mrmackey dhcpcd[622]: eth0: deleting default route via
192.168.0.1
Apr 05 02:00:30 mrmackey systemd-timesyncd[364]: System time changed. Resyncing.
Apr 05 02:00:30 mrmackey systemd-sleep[807]: System resumed.
Apr 05 02:00:30 mrmackey systemd[1]: Requested transaction contradicts existing
jobs: File exists
Apr 05 02:00:30 mrmackey systemd-logind[543]: Operation finished.
Apr 05 02:00:32 mrmackey dhcpcd[622]: eth0: carrier acquired
Apr 05 02:00:32 mrmackey kernel: r8169 0000:02:00.0 eth0: link up
Apr 05 02:00:32 mrmackey dhcpcd[622]: eth0: soliciting an IPv6 router
Apr 05 02:00:32 mrmackey dhcpcd[622]: eth0: rebinding lease of 192.168.0.25
Apr 05 02:00:41 mrmackey dhcpcd[622]: eth0: leased 192.168.0.25 for 86400
seconds
Apr 05 02:00:41 mrmackey dhcpcd[622]: eth0: adding host route to 192.168.0.25
via 127.0.0.1
Apr 05 02:00:41 mrmackey dhcpcd[622]: eth0: adding route to 192.168.0.0/24
Apr 05 02:00:41 mrmackey dhcpcd[622]: eth0: adding default route via 192.168.0.1
Apr 05 02:00:44 mrmackey dhcpcd[622]: eth0: no IPv6 Routers available
.... happily overwrote the manual interface configuration, causing the
box to get the wrong IP, breakage ensued.
There used to be log entries like:
Mär 31 10:30:43 mrmackey dhcpcd[543]: Not running dhcpcd because
/etc/network/interfaces ... failed!
Mär 31 10:30:43 mrmackey dhcpcd[543]: defines some interfaces that will use a
DHCP client ... failed!
Mär 31 10:30:43 mrmackey systemd[1]: dhcpcd.service: control process exited,
code=exited status=6
Mär 31 10:30:43 mrmackey systemd[1]: Failed to start LSB: IPv4 DHCP client with
IPv4LL support.
Mär 31 10:30:43 mrmackey systemd[1]: Unit dhcpcd.service entered failed state.
But that was the last one of this kind. dhcpcd ran without really
doing anything on the 1st and 2nd, then assigned the wrong IP on the
3rd, 4th and 5th. So it's basically on the fritz since the 8.4 update,
but the trigger may just as well have been the (rare) reboot that
followed it, not anything in the update itself.
/etc/network/interfaces is attached, I really don't see why it should
be running at all. I'm purging it for now, just to be sure, but I can
always reinstall it for tests.
Regards,
Christian
-- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dhcpcd5 depends on:
ii libc6 2.19-18+deb8u4
Versions of packages dhcpcd5 recommends:
pn openresolv | resolvconf <none>
Versions of packages dhcpcd5 suggests:
pn dhcpcd-gtk <none>
-- no debconf information
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug eth0
auto eth0
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.0.5
netmask 255.255.255.0
gateway 192.168.0.1
mtu 9000
ethernet-wol g
# wifi experiemnts
#allow-hotplug wlan0
#iface wlan0 inet dhcp
# wpa-driver nl80211
# wpa-ssid Southpark
# wpa-psk XXXXXXXXXX
