Package: ifupdown
Version: 0.8.32
Severity: normal
Hello,
My wlo1 configuration reads as:
iface wlo1 inet dhcp
wpa-conf /etc/wpa_supplicant.conf
when I ifup wlo1, ifup starts the dhcp client immediately, without
waiting for wpa_supplicant to actually negociate the link. This is
deemed to fail, the first DHCPDISCOVER will for sure get lost since the
link is not up yet. As a consequence, one systematically has to wait for
the random delay before the dhcp client sends another DHCPDISCOVER.
ifupdown could wait for the link carrier to get up before starting the
dhcp client, which would then most probably always succeed on first try,
and not need random retry delays.
Samuel
-- 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
# The primary network interface
#allow-hotplug enp0s25
iface enp0s25 inet dhcp
auto enp0s25:0
#iface enp0s25:0 inet static
# address 169.254.255.8
# netmask 255.255.0.0
iface wlo1 inet dhcp
wpa-conf /etc/wpa_supplicant.conf
iface wlo1:0 inet6 static
address fec0::2
netmask 64
#iface wlo1 inet static
# address 151.216.4.70
# netmask 255.255.254.0
# gateway 151.216.4.1
# wireless_essid RMLL2012-FIXE
# address 10.0.0.1
# netmask 255.0.0.0
# wireless_mode ad-hoc
# wireless_essid blip
# wireless_channel 1
#auto br129
#iface br129 inet manual
# bridge_ports dummy0
# bridge_stp off
--- /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 16
-rwxr-xr-x 1 root root 289 Jan 17 2018 bind9
-rwxr-xr-x 1 root root 1677 Sep 1 2017 clamav-freshclam-ifupdown
-rwxr-xr-x 1 root root 372 Jul 7 2015 openvpn
-rwxr-xr-x 1 root root 256 Jun 3 2015 resolvconf
lrwxrwxrwx 1 root root 32 Jun 8 14:30 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-post-down.d:
total 4
lrwxrwxrwx 1 root root 29 Apr 8 23:06 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root 1409 Mar 24 2016 wireless-tools
lrwxrwxrwx 1 root root 32 Jun 8 14:30 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-pre-up.d:
total 12
lrwxrwxrwx 1 root root 29 Apr 8 23:06 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root 344 Sep 22 2014 ethtool
-rwxr-xr-x 1 root root 4178 Mar 24 2016 wireless-tools
lrwxrwxrwx 1 root root 32 Jun 8 14:30 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
/etc/network/if-up.d:
total 36
-rwxr-xr-x 1 root root 817 Jun 3 2015 000resolvconf
-rwxr-xr-x 1 root root 289 Jan 17 2018 bind9
-rwxr-xr-x 1 root root 1677 Sep 1 2017 clamav-freshclam-ifupdown
-rwxr-xr-x 1 root root 1685 Sep 22 2014 ethtool
-rwxr-xr-x 1 root root 4958 May 20 2015 mountnfs
-rwxr-xr-x 1 root root 900 Apr 28 2016 ntpdate
-rwxr-xr-x 1 root root 972 Mar 30 2017 openssh-server
-rwxr-xr-x 1 root root 385 Jul 7 2015 openvpn
lrwxrwxrwx 1 root root 32 Jun 8 14:30 wpasupplicant ->
../../wpa_supplicant/ifupdown.sh
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1,
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ifupdown depends on:
ii adduser 3.117
ii iproute2 4.17.0-2
ii libc6 2.27-3
ii lsb-base 9.20170808
Versions of packages ifupdown recommends:
ii isc-dhcp-client [dhcp-client] 4.3.5-4
Versions of packages ifupdown suggests:
ii ppp 2.4.7-2+3
ii rdnssd 1.0.3-3
-- no debconf information
--
Samuel
There are two types of Linux developers - those who can spell, and
those who can't. There is a constant pitched battle between the two.
(From one of the post-1.1.54 kernel update messages posted to c.o.l.a)
