Package: wpasupplicant
Version: 2:2.7+git20190128+0c1e29f-6+deb10u2
Severity: important
Dear Maintainer,
* What led up to the situation?
Regular wpasupplicant + backports kernel updates
* What exactly did you do (or not do) that was effective (or
ineffective)?
Removing custom module parameters for iwlwifi module did not solve problem
Configuring interface manually using the wlp36s0 device worked
* What was the outcome of this action?
Card was only able to associate with WLAN and connect successfully when
enabled manually
* What outcome did you expect instead?
Connection to WLAN should have Just Worked as it has in the past
-- System Information:
Debian Release: 10.8
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wpasupplicant depends on:
ii adduser 3.118
ii libc6 2.28-10
ii libdbus-1-3 1.12.20-0+deb10u1
ii libnl-3-200 3.4.0-1
ii libnl-genl-3-200 3.4.0-1
ii libnl-route-3-200 3.4.0-1
ii libpcsclite1 1.8.24-1
ii libreadline7 7.0-5
ii libssl1.1 1.1.1d-0+deb10u5
ii lsb-base 10.2019051400
wpasupplicant recommends no packages.
Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl <none>
pn wpagui <none>
-- no debconf information
I'm not quite sure when it happened (it's been an age since the last reboot) but
I recently discovered that the wireless network on one of my machines wouldn't
come up at boot.
To cut a long story short, it looks like wpasupplicant was throwing an error
when bringing up the interface. Networking status pointed at a device that I
don't recall seeing before, p2p-dev-wlp39s0. Because wpasupplicant threw an
error, the rest of the networking steps were never performed (so I was left
without a default gateway etc):
/etc/init.d/networking status
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2021-03-21 22:18:34 GMT;
6min ago
Docs: man:interfaces(5)
Process: 22444 ExecStart=/sbin/ifup -a --read-environment (code=exited,
status=1/FAILURE)
Main PID: 22444 (code=exited, status=1/FAILURE)
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: Failed to open
/proc/sys/net/ipv4/conf/p2p-dev-wlp36s0/drop_unicast_in_l2_multicast: No
such file or directory
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: Failed to set IPv4
unicast in multicast filter
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: Failed to open
/proc/sys/net/ipv4/conf/p2p-dev-wlp36s0/drop_unicast_in_l2_multicast: No
such file or directory
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: Failed to set IPv4
unicast in multicast filter
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: deinit
ifname=p2p-dev-wlp36s0 disabled_11b_rates=0
Mar 21 22:18:34 macduff wpa_supplicant[22472]: p2p-dev-wlp36s0:
CTRL-EVENT-TERMINATING
Mar 21 22:18:34 macduff wpa_supplicant[22472]: nl80211: deinit
ifname=wlp36s0 disabled_11b_rates=0
Mar 21 22:18:34 macduff wpa_supplicant[22472]: wlp36s0:
CTRL-EVENT-TERMINATING
Mar 21 22:18:34 macduff systemd[1]: networking.service: Failed with result
'exit-code'.
Mar 21 22:18:34 macduff systemd[1]: Failed to start Raise network interfaces.
The same device showed up in /var/run/wpa_supplicant and wpa_cli (MACs and UIDs
removed):
wpa_cli status
Selected interface 'p2p-dev-wlp36s0'
wpa_state=DISCONNECTED
p2p_device_address=
address=
uuid=
According to the doc, wpasupplicant will try and bring up the first device it
sees in /var/run/wpa_supplicant which appears to be the wrong one.
Manually upping wlp36s0 with ifup worked but every attempt using the networking
script/wpasupplicant failed and left me with an unconfigured network. Using the
"correct" device name I'm able to connect successfully.
wpa_cli status -i wlp36s0
bssid=
freq=5500
ssid=
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=
p2p_device_address=
address=
uuid=
ieee80211ac=1
I was using some custom parameters for the iwlwifi and kernel boot but I
disabled those for the purposes of debugging. The wireless card in question is
an Intel 8265 using the v36 firmware. iw reports that this device supports P2P,
whatever that means. From dmesg:
[ 3.996170] iwlwifi 0000:24:00.0: firmware: direct-loading firmware
iwlwifi-8265-36.ucode
[ 3.997288] iwlwifi 0000:24:00.0: loaded firmware version 36.9f0a2d68.0
8265-36.ucode op_mode iwlmvm
[ 3.997528] iwlwifi 0000:24:00.0: firmware: failed to load
iwl-debug-yoyo.bin (-2)
[ 4.184298] iwlwifi 0000:24:00.0: Detected Intel(R) Dual Band Wireless AC
8265, REV=0x230
I'm using debian stable with the exception of the buster backports 5.10 kernel
(I think the previous kernel I was running on was the 5.8 backports version but
the same issue occurs with the 4.19 stable kernel too).
From my point of view it seems like wpasupplicant is trying to use a "wrong"
non-existent interface but I confess I don't really know what the P2P device is
and I don't know if it was there previously but it seems to be what's breaking
my networking config. Does anyone know if its existence is legitimate or how I
can get wpasupplicant to stop creating/using it? Or am I on the wrong track with
the device name?
