Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

[Lisandro Damián Nicanor Pérez Meyer]

Package: wpasupplicant
Version: 2.6-2
Severity: serious
Justification: Makes package unusable

I upgraded form testing's 2.5-2+v2.4-3+b1 to sid's 2.6-2 and I can't no
longer connect to encrypted WiFi networks.

Going back to the version in testing makes my WiFI work again.

With 2.6-2 I'm getting:

wpa_supplicant[868]: wlp12s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-
debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages wpasupplicant depends on:
ii adduser 3.115
ii libc6 2.24-8
ii libdbus-1-3 1.10.14-1
ii libnl-3-200 3.2.27-1
ii libnl-genl-3-200 3.2.27-1
ii libpcsclite1 1.8.19-1
ii libreadline7 7.0-1
ii libssl1.1 1.1.0c-2
ii lsb-base 9.20161125

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl <none>
pn wpagui <none>

-- no debconf information

[Andrew Shadura]

Hi,

On 22 December 2016 at 15:22, Lisandro Damián Nicanor Pérez Meyer

<perez...@gmail.com> wrote:
> Package: wpasupplicant
> Version: 2.6-2
> Severity: serious
> Justification: Makes package unusable
>
> I upgraded form testing's 2.5-2+v2.4-3+b1 to sid's 2.6-2 and I can't no
> longer connect to encrypted WiFi networks.
>
> Going back to the version in testing makes my WiFI work again.
>
> With 2.6-2 I'm getting:
>
> wpa_supplicant[868]: wlp12s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1

Any more details please? I've been using this for a month at least
with no issues.

--
Cheers,
Andrew

[Lisandro Damián Nicanor Pérez Meyer]

Not that I can imagine of, but please do not heasitate in telling me which details/data might help you.

So far all I know is what I wrote above.

--

Lisandro Damián Nicanor Pérez Meyer

http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

[Andrew Shadura]

Hi,

On 22 December 2016 at 16:46, Lisandro Damián Nicanor Pérez Meyer

<perez...@gmail.com> wrote:
> Not that I can imagine of, but please do not heasitate in telling me which
> details/data might help you.
>
> So far all I know is what I wrote above.

Well, first of all please tell me what hardware you use, and then try
to get more logs please, especially those wpa_supplicant produces with
-dt (you can add it with a systemd override file).


--
Cheers,
Andrew

[Lisandro Damián Nicanor Pérez Meyer]

Sure thing! Tip: consider adding a reportbug template to src:wpa to indicate
users to gather this info before filling bugs.

0c:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless
LAN Controller (rev 01) using broadcom-sta-dkms to get the proprietary driver
(sadly the libre one hangs too much). Note: I've checked with both the testing
and sid versions of broadcom-sta-dkms and both fail in the same way.

I could not make the systemd override file, but stopping the service and
running it by hand gave me:

# /sbin/wpa_supplicant -d -t -u -s -O /run/wpa_supplicant
1482423134.657501: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423135.666339: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423137.669924: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423138.671601: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423140.675264: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423141.677033: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423143.680702: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
1482423144.682873: Scan SSID - hexdump_ascii(len=8):
68 65 72 6d 69 6f 6e 65 hermione
[more like this...]

This log happened while trying quite a lot of times to connect.

As an interesting note: even if I was running wpa_supplicant "by hand", after
downgrading the package in order to be able to send this mail I had to reboot
the computer to make it work.

Of course feel free to send more more debugging tips as you need.

Thanks!

--
Cuando alguna persona va al ataque contra Wikipedia argumentando
que no es confiable "porque encontró ya varios errores", hago la
siguiente pregunta: "¿Corregiste esos errores cuando los
encontraste?" Invariablemente, la respuesta es "no".
Ariel Torres, "Probablemente, la Wikipedia esté bien"
La Nación Tecnología, Sábado 25 de agosto de 2007
http://www.lanacion.com.ar/tecnologia/nota.asp?nota_id=937889

Lisandro Damián Nicanor Pérez Meyer

http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

[Andrew Shadura]

On 22/12/16 17:41, Andrew Shadura wrote:

> On 22/12/16 17:23, Lisandro Damián Nicanor Pérez Meyer wrote:
>> 0c:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless
>> LAN Controller (rev 01) using broadcom-sta-dkms to get the proprietary driver
>> (sadly the libre one hangs too much). Note: I've checked with both the testing
>> and sid versions of broadcom-sta-dkms and both fail in the same way.
>>
>> I could not make the systemd override file, but stopping the service and
>> running it by hand gave me:
>>
>> # /sbin/wpa_supplicant -d -t -u -s -O /run/wpa_supplicant
>> 1482423134.657501: Scan SSID - hexdump_ascii(len=8):
>> 68 65 72 6d 69 6f 6e 65 hermione
>

>> This log happened while trying quite a lot of times to connect.
>>
>> As an interesting note: even if I was running wpa_supplicant "by hand", after
>> downgrading the package in order to be able to send this mail I had to reboot
>> the computer to make it work.
>>
>> Of course feel free to send more more debugging tips as you need.
>

> Sadly, that doesn't give much information to me. However, googling for
> the exact error code together with the hardware led me to this:
>
> https://bbs.archlinux.org/viewtopic.php?pid=1216302#p1216302
>
> I don't know whether that makes sense or not, but could you please try that?

Also, there's https://bugs.debian.org/833507 and a related
https://bugs.debian.org/838096, could you please check whether they're
related to your failure?

--
Cheers,
Andrew

[Andrew Shadura]

On 22/12/16 17:23, Lisandro Damián Nicanor Pérez Meyer wrote:
> 0c:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless
> LAN Controller (rev 01) using broadcom-sta-dkms to get the proprietary driver
> (sadly the libre one hangs too much). Note: I've checked with both the testing
> and sid versions of broadcom-sta-dkms and both fail in the same way.
>
> I could not make the systemd override file, but stopping the service and
> running it by hand gave me:
>
> # /sbin/wpa_supplicant -d -t -u -s -O /run/wpa_supplicant
> 1482423134.657501: Scan SSID - hexdump_ascii(len=8):
> 68 65 72 6d 69 6f 6e 65 hermione

> This log happened while trying quite a lot of times to connect.
>
> As an interesting note: even if I was running wpa_supplicant "by hand", after
> downgrading the package in order to be able to send this mail I had to reboot
> the computer to make it work.
>
> Of course feel free to send more more debugging tips as you need.

Sadly, that doesn't give much information to me. However, googling for
the exact error code together with the hardware led me to this:

https://bbs.archlinux.org/viewtopic.php?pid=1216302#p1216302

I don't know whether that makes sense or not, but could you please try that?

--
Cheers,
Andrew

[Scott Mcdermott]

my machine is having an identical looping scan failure
messages as did the submitter after recent update.

worked: 2.5-2+v2.4-3+b1
broken: 2.6-2
device: 03:00.0 Network controller: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter (rev 03)
driver: Broadcom BCM43a0 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
ifupdown: 0.8.16
broadcom-sta-dkms: 6.30.223.271-5

/etc/network/interfaces.d/wlan0-supplicant:
iface wlan0 inet dhcp
wpa-driver nl80211
wpa-conf /etc/wifirc
wpa-debug-level 3

/etc/wifirc:
ap_scan=1
network={
ssid="myssid"
psk="mypassword"
}
...

notes:
- computer is a mbpr 11,1
- rfkill shows as allowed
- tried rebuilding dkms, does not work
- tried reloading wl.ko, does not work
- reboot after downgrade wasn't needed, worked right away
- not using systemd or NetworkManager (not installed)
- no driver backtraces exist in my syslogs
- new wpasupplicant *does* work ok with a usb rtl8187

EOM

(syslog below)

: wpa_supplicant v2.6
: random: Trying to read entropy from /dev/random
: Successfully initialized wpa_supplicant
: Initializing interface 'wlan0' conf '/etc/wifirc' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
: Configuration file '/etc/wifirc' -> '/etc/wifirc'
: Reading configuration file '/etc/wifirc'
: update_config=1
: ap_scan=1
: ctrl_interface='DIR=/var/run/wpa_supplicant'
: Line: 17 - start of a new network block
: priority=5 (0x5)
: PSK (from passphrase) - hexdump(len=32): [REMOVED]
: Priority group 5
: id=0 ssid='myssid'
: nl80211: Supported cipher 00-0f-ac:1
: nl80211: Supported cipher 00-0f-ac:5
: nl80211: Supported cipher 00-0f-ac:2
: nl80211: Supported cipher 00-0f-ac:4
: nl80211: Supported cipher 00-0f-ac:6
: nl80211: interface wlan0 in phy phy0
: nl80211: Set mode ifindex 3 iftype 2 (STATION)
: nl80211: Subscribe to mgmt frames with non-AP handle 0x5573e8060fe0
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=040a
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 04 0a
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=040b
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 04 0b
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=040c
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 04 0c
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=040d
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 04 0d
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=090a
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 09 0a
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=090b
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 09 0b
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=090c
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 09 0c
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=090d
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 09 0d
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0409506f9a09
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=7f506f9a09
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0801
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 08 01
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=06
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=1): 06
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0a07
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 0a 07
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0a11
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 0a 11
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=1101
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 11 01
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=1102
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 11 02
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0505
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 05 05
: nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x5573e8060fe0 match=0500
: nl80211: Register frame command failed (type=208): ret=-95 (Operation not supported)
: nl80211: Register frame match - hexdump(len=2): 05 00
: nl80211: Failed to register Action frame processing - ignore for now
: rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=0
: netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
: Add interface wlan0 to a new radio phy0
: nl80211: Regulatory information - country=00
: nl80211: 2402-2472 @ 40 MHz 20 mBm
: nl80211: 2457-2482 @ 20 MHz 20 mBm (no IR)
: nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
: nl80211: 5170-5250 @ 80 MHz 20 mBm (no IR)
: nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS) (no IR)
: nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
: nl80211: 5735-5835 @ 80 MHz 20 mBm (no IR)
: nl80211: 57240-63720 @ 2160 MHz 0 mBm
: nl80211: Added 802.11b mode based on 802.11g information
: wlan0: Own MAC address: 3c:15:c2:aa:bb:cc
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
: wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
: wlan0: RSN: flushing PMKID list in the driver
: nl80211: Flush PMKIDs
: wlan0: Setting scan request: 0.100000 sec
: TDLS: TDLS operation not supported by driver
: TDLS: Driver uses internal link setup
: TDLS: Driver does not support TDLS channel switching
: wlan0: WPS: UUID based on MAC address: 211e8a77-c908-5644-a5b3-e8ec52bbe890
: ENGINE: Loading dynamic engine
: ENGINE: Loading dynamic engine
: EAPOL: SUPP_PAE entering state DISCONNECTED
: EAPOL: Supplicant port status: Unauthorized
: nl80211: Skip set_supp_port(unauthorized) while not associated
: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
: EAPOL: SUPP_BE entering state INITIALIZE
: EAP: EAP entering state DISABLED
: wlan0: Added interface wlan0
: wlan0: State: DISCONNECTED -> DISCONNECTED
: nl80211: Set wlan0 operstate 0->0 (DORMANT)
: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
: Daemonize..
: random: Got 20/20 bytes from /dev/random
: RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=6 linkmode=0 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
: RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=5 linkmode=0 ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
: RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=5 linkmode=1 ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
: wlan0: State: DISCONNECTED -> SCANNING
: wlan0: Starting AP scan for wildcard SSID
: wlan0: Add radio work 'scan'@0x5573e8083620
: wlan0: First radio work item in the queue - schedule start immediately
: wlan0: Starting radio work 'scan'@0x5573e8083620 after 0.000008 second wait
: wlan0: nl80211: scan request
: nl80211: Scan extra IEs - hexdump(len=6): 7f 04 00 00 0a 02
: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
: wlan0: State: SCANNING -> DISCONNECTED
: nl80211: Set wlan0 operstate 0->0 (DORMANT)
: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
: wlan0: Radio work 'scan'@0x5573e8083620 done in 0.000088 seconds
: wlan0: radio_work_free('scan'@0x5573e8083620: num_active_works --> 0
: wlan0: Setting scan request: 1.000000 sec
: EAPOL: disable timer tick
: wlan0: State: DISCONNECTED -> SCANNING
: wlan0: Starting AP scan for wildcard SSID
: wlan0: Add radio work 'scan'@0x5573e8083620
: wlan0: First radio work item in the queue - schedule start immediately
: wlan0: Starting radio work 'scan'@0x5573e8083620 after 0.000016 second wait
: wlan0: nl80211: scan request
: nl80211: Scan extra IEs - hexdump(len=6): 7f 04 00 00 0a 02
: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
: wlan0: State: SCANNING -> DISCONNECTED
: nl80211: Set wlan0 operstate 0->0 (DORMANT)
: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
: wlan0: Radio work 'scan'@0x5573e8083620 done in 0.000089 seconds
: wlan0: radio_work_free('scan'@0x5573e8083620: num_active_works --> 0
: wlan0: Setting scan request: 1.000000 sec
: wlan0: State: DISCONNECTED -> SCANNING
: wlan0: Starting AP scan for wildcard SSID
: wlan0: Add radio work 'scan'@0x5573e8083620
: wlan0: First radio work item in the queue - schedule start immediately
: wlan0: Starting radio work 'scan'@0x5573e8083620 after 0.000024 second wait
: wlan0: nl80211: scan request
: nl80211: Scan extra IEs - hexdump(len=6): 7f 04 00 00 0a 02
: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
: wlan0: State: SCANNING -> DISCONNECTED
: nl80211: Set wlan0 operstate 0->0 (DORMANT)
: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
: wlan0: Radio work 'scan'@0x5573e8083620 done in 0.000120 seconds
: wlan0: radio_work_free('scan'@0x5573e8083620: num_active_works --> 0
: wlan0: Setting scan request: 1.000000 sec
: wlan0: State: DISCONNECTED -> SCANNING
: wlan0: Starting AP scan for wildcard SSID
: wlan0: Add radio work 'scan'@0x5573e8083620
: wlan0: First radio work item in the queue - schedule start immediately
: wlan0: Starting radio work 'scan'@0x5573e8083620 after 0.000029 second wait
: wlan0: nl80211: scan request
: nl80211: Scan extra IEs - hexdump(len=6): 7f 04 00 00 0a 02
: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
: wlan0: State: SCANNING -> DISCONNECTED
: nl80211: Set wlan0 operstate 0->0 (DORMANT)
: netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
...

[Lisandro Damián Nicanor Pérez Meyer]

Thanks to Eduard Bloch at [bug] I've tried adding

[device]
wifi.scan-rand-mac-address=no

to /etc/NetworkManager/NetworkManager.conf

and updating wpasupplicant... and voilá, WiFi is on again.

[bug] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849034#15>

I don't know if it's a bug in the driver, NM or wpasupplicant, but at least
things now work.

Cheers, Lisandro.

--

Lisandro Damián Nicanor Pérez Meyer

http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

[Lisandro Damián Nicanor Pérez Meyer]

On lunes, 26 de diciembre de 2016 20:04:08 ART Andrew Shadura wrote:

> On 26/12/16 19:28, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Thanks to Eduard Bloch at [bug] I've tried adding
> >
> > [device]
> > wifi.scan-rand-mac-address=no
> >
> > to /etc/NetworkManager/NetworkManager.conf
> >
> > and updating wpasupplicant... and voilá, WiFi is on again.
> >
> > [bug] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849034#15>
> >
> > I don't know if it's a bug in the driver, NM or wpasupplicant, but at
> > least
> > things now work.
>

> Lisandro, what NM version are you using? A related bug has been fixed by
> mbiebl recently:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835822#67

Interesting. I was using 1.4.2-3. After trying this workaround/fix I updated
to 1.4.4-1 which is what I'm currently using.

Thanks!

--
Quizá, para muchos, ahora que lo pienso, Wikipedia tiene
ciertamente un defecto imperdonable. No adorna.

Ariel Torres, "Probablemente, la Wikipedia esté bien"
La Nación Tecnología, Sábado 25 de agosto de 2007
http://www.lanacion.com.ar/tecnologia/nota.asp?nota_id=937889

[Andrew Shadura]

On Mon, 26 Dec 2016 16:39:43 -0300 Lisandro
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer <perez...@gmail.com>
wrote:

> On lunes, 26 de diciembre de 2016 20:04:08 ART Andrew Shadura wrote:
> > On 26/12/16 19:28, Lisandro Damián Nicanor Pérez Meyer wrote:
> > > Thanks to Eduard Bloch at [bug] I've tried adding
> > >
> > > [device]
> > > wifi.scan-rand-mac-address=no
> > >
> > > to /etc/NetworkManager/NetworkManager.conf
> > >
> > > and updating wpasupplicant... and voilá, WiFi is on again.
> > >
> > > [bug] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849034#15>
> > >
> > > I don't know if it's a bug in the driver, NM or wpasupplicant, but at
> > > least
> > > things now work.
> >
> > Lisandro, what NM version are you using? A related bug has been fixed by
> > mbiebl recently:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835822#67
>
> Interesting. I was using 1.4.2-3. After trying this workaround/fix I updated
> to 1.4.4-1 which is what I'm currently using.
>
> Thanks!

Lisandro, could you please confirm this indeed was the issue with MAC
randomization and it indeed is solved by an NM update?

--
Cheers,
Andrew

[Michael Biebl]

On Tue, 10 Jan 2017 15:36:06 -0300 Lisandro
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer <perez...@gmail.com>
wrote:
> On martes, 10 de enero de 2017 17:24:00 ART Andrew Shadura wrote:
> [snip]

> > Lisandro, could you please confirm this indeed was the issue with MAC
> > randomization and it indeed is solved by an NM update?
>

> No, not solved by the NM update. To avoid the bug I still need to configure NM
> to disable randomization.
>
> That being said I have no clue who's at fault: NM, wpa-supplicant, the wifi's
> driver or a specific mix of them.

It's most likely a driver or rather hardware specific issue, exposed by
the fact that NM enables that address randomization feature, which in
turn requires wpasupplicant 2.5+ for it to work iirc.
By turning it off in NM or downgrading wpasupplicant, you simply avoid
that problem.

I was pointed at [1] by NM upstream.
Lisandro, it might make sense to follow up upstream, so your card is
included in that list as well (with a log file as Thomas suggested)

Andrew, since you've been asking on IRC: if this turns out to be a huge
problem for many users, we can change that default in NM. For now it
looks like isolated incidents so I'd keep the current configuration for now.

If you see more bug reports coming in related to this issue, please let
me know and we can re-evaluate this decision.

Michael

[1] https://bugzilla.gnome.org/show_bug.cgi?id=775529
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[Nicolas Kuttler]

On 2017-11-25 10:06, Andrew Shadura wrote:
> I've just uploaded wpa 2.6 into unstable once again. Please upgrade,
> test and let me know if it works for you.

Hm, installing wpasupplicant:amd64 2:2.6-8 lead to me not being able to
connect to wireless networks again.

Adding the following lines to /etc/NetworkManager/NetworkManager.conf
fixed this problem:

[device]
wifi.scan-rand-mac-address=no

[Andrew Shadura]

Okay, thanks.

I'm losing my patience with this issue, so I am just going to ship this
snippet within the wpasupplicant package.

--
Cheers,
Andrew