Package: ifupdown
Version: 0.8.35
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded a machine from stretch to buster. It had an assigned static
IP of 204.122.16.15. The machine ran fine for two days then disappeared from
the network.
Upon investigation I found it had a 169.254.x.x address assigned in
addition to the staticly assigned address. The routing table showed this
in with a route scope of local and my default route still there but the machine
would not route to the Internet with this IP address on the interface and the
bogus route in place.
Removing the IP caused ALL routes to be deleted from the routing table,
and then manually adding them back in allowed the machine to work again for
a while, then it did it again.
It seemed the DHCP client kept trying to assign this bogus address to
the interface.
Deleting the DHCP client from the system fixed this issue but this should
not be necessary. It should not add a second IP to an interface with an
assigned static IP AND even if it did the route should not have interfered
with the default route but it did.
This is, to put it mildly, extremely unfriendly network behavior.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Deleting the DHCP client fixed the issue for me but this is obviously
undesirable for people without static IP space.
* What was the outcome of this action?
After deleting the DHCP client my machine operated as expected. Also,
it booted nearly instantly where as before there was considerable delay while
DHCP tried to acquire an address even though the Interface had a static IP.
* What outcome did you expect instead?
I expect that if I have an interface configured with a static IP via
the Network Manager, DHCP client should NOT run on that interface at all.
*** End of the template - remove these template lines ***
-- Package-specific info:
--- /etc/network/interfaces:
# 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
--- /etc/network/interfaces.d/*:
cat: '/etc/network/interfaces.d/*': No such file or directory
--- up and down scripts installed:
/etc/network/if-down.d:
total 0
lrwxrwxrwx 1 root root 32 Jun 6 06:16 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-post-down.d:
total 4
lrwxrwxrwx 1 root root 23 Oct 10 2018 avahi-daemon -> ../if-up.d/avahi-daemon
-rwxr-xr-x 1 root root 1409 Jun 5 2018 wireless-tools
lrwxrwxrwx 1 root root 32 Jun 6 06:16 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-pre-up.d:
total 8
-rwxr-xr-x 1 root root 4191 Sep 15 2018 wireless-tools
lrwxrwxrwx 1 root root 32 Jun 6 06:16 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-up.d:
total 4
-rwxr-xr-x 1 root root 484 Apr 27 2018 avahi-daemon
lrwxrwxrwx 1 root root 32 Jun 6 06:16 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
-- System Information:
Debian Release: 10.0
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ifupdown depends on:
ii adduser 3.118
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii lsb-base 10.2019051400
Versions of packages ifupdown recommends:
pn isc-dhcp-client | dhcp-client <none>
Versions of packages ifupdown suggests:
ii ppp 2.4.7-2+4.1
pn rdnssd <none>
-- no debconf information
