FS#61119 - [wpa_supplicant] Passes invalid arguments to broadcom-wl driver

Attached to Project: Arch Linux
Opened by Colin Unger (lockshaw) - Tuesday, 18 December 2018, 07:38 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 16 January 2019, 20:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 46
Private No

Details

Description:
When using the broadcom-wl driver (version 6.30.223.271), wpa_supplicant is not able to authenticate to networks because it passes invalid arguments to the wl driver. This works in version 2.6, but fails in 2.7.

It may be similar to the bug report here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833507 (though the current Arch config does not appear to include the CONFIG_WNM or CONFIG_WNM_AP options, so it doesn't seem to be identical).

I am not sure if this should be filed as a bug here or upstream, but since other distros had handled similar problems at the distro level, I figured I would start here.

Additional info:
* wpa_supplicant (1:2.7-1)
* broadcom-wl-dkms (version 6.30.223.271)

Below is an excerpt form the wpa_supplicant logs with verbose debugging enabled:
```
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: Starting AP scan for wildcard SSID (Interleave with specific)
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: Add radio work 'scan'@0x55a3451483b0
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: First radio work item in the queue - schedule start immediately
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: Starting radio work 'scan'@0x55a3451483b0 after 0.000007 second wait
Dec 17 21:41:34 freya wpa_supplicant[24157]: Request driver to clear scan cache due to local BSS flush
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: nl80211: scan request
Dec 17 21:41:34 freya wpa_supplicant[24157]: nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
Dec 17 21:41:34 freya wpa_supplicant[24157]: nl80211: Scan extra IEs - hexdump(len=12): 7f 0a 00 00 00 00 00 00 00 00 00 01
Dec 17 21:41:34 freya wpa_supplicant[24157]: nl80211: Add NL80211_SCAN_FLAG_FLUSH
Dec 17 21:41:34 freya wpa_supplicant[24157]: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: State: SCANNING -> INACTIVE
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: Radio work 'scan'@0x55a3451483b0 done in 0.000068 seconds
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: radio_work_free('scan'@0x55a3451483b0): num_active_works --> 0
Dec 17 21:41:34 freya wpa_supplicant[24157]: wlp2s0: Setting scan request: 1.000000 sec
Dec 17 21:41:34 freya wpa_supplicant[24157]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/0
Dec 17 21:41:35 freya wpa_supplicant[24157]: dbus: fi.w1.wpa_supplicant1.Interface.RemoveNetwork (/fi/w1/wpa_supplicant1/Interfaces/0) [o]
Dec 17 21:41:35 freya wpa_supplicant[24157]: dbus: Unregister network object '/fi/w1/wpa_supplicant1/Interfaces/0/Networks/0'
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 state=INACTIVE
Dec 17 21:41:35 freya wpa_supplicant[24157]: TDLS: Tear down peers
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Data frame filter flags=0x0
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: State: INACTIVE -> DISCONNECTED
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Set wlp2s0 operstate 0->0 (DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: netlink: Operstate: ifindex=2 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: EAPOL: External notification - portEnabled=0
Dec 17 21:41:35 freya wpa_supplicant[24157]: EAPOL: External notification - portValid=0
Dec 17 21:41:35 freya wpa_supplicant[24157]: RTM_NEWLINK: ifi_index=2 ifname=wlp2s0 operstate=5 linkmode=1 ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Dec 17 21:41:35 freya wpa_supplicant[24157]: RTM_NEWLINK: ifi_index=2 ifname=wlp2s0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1002 ()
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Interface down (wlp2s0/wlp2s0)
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Event INTERFACE_DISABLED (26) received
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Interface was disabled
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Data frame filter flags=0x0
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: State: DISCONNECTED -> DISCONNECTED
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Set wlp2s0 operstate 0->0 (DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: netlink: Operstate: ifindex=2 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: EAPOL: External notification - portEnabled=0
Dec 17 21:41:35 freya wpa_supplicant[24157]: EAPOL: External notification - portValid=0
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: State: DISCONNECTED -> INTERFACE_DISABLED
Dec 17 21:41:35 freya wpa_supplicant[24157]: l2_packet_receive - recvfrom: Network is down
Dec 17 21:41:35 freya wpa_supplicant[24157]: RTM_NEWLINK: ifi_index=2 ifname=wlp2s0 operstate=5 linkmode=1 ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Interface up (wlp2s0/wlp2s0)
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Own MAC address on ifindex 2 (wlp2s0) changed from 6c:40:08:8f:f9:d6 to ba:c1:d2:34:32:9f
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Event INTERFACE_ENABLED (25) received
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Interface was enabled
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: State: INTERFACE_DISABLED -> DISCONNECTED
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Set wlp2s0 operstate 0->0 (DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: netlink: Operstate: ifindex=2 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Rescheduling scan request: 0.000000 sec
Dec 17 21:41:35 freya wpa_supplicant[24157]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/0
Dec 17 21:41:35 freya wpa_supplicant[24157]: dbus: fi.w1.wpa_supplicant1.Interface.Scan (/fi/w1/wpa_supplicant1/Interfaces/0) [a{sv}]
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Add radio work 'scan'@0x55a3451483b0
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: First radio work item in the queue - schedule start immediately
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: No enabled networks - do not scan
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: State: DISCONNECTED -> INACTIVE
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: Starting radio work 'scan'@0x55a3451483b0 after 0.000043 second wait
Dec 17 21:41:35 freya wpa_supplicant[24157]: Request driver to clear scan cache due to local BSS flush
Dec 17 21:41:35 freya wpa_supplicant[24157]: wlp2s0: nl80211: scan request
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Scan SSID - hexdump_ascii(len=0): [NULL]
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Add NL80211_SCAN_FLAG_FLUSH
Dec 17 21:41:35 freya wpa_supplicant[24157]: Scan requested (ret=0) - scan timeout 30 seconds
Dec 17 21:41:35 freya wpa_supplicant[24157]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/0
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Event message available
Dec 17 21:41:35 freya wpa_supplicant[24157]: nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlp2s0
```

Steps to reproduce:
1. Use a computer with a broadcom network card that requires the broadcom-wl driver
2. Scan for networks (or try to connect to a wpa-authenticated network) with wpa_supplicant (or, in my case, NetworkManager)
3. The scan will fail and log the above failures
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Wednesday, 16 January 2019, 20:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  wpa_supplicant 2:2.6-1
Comment by Chris (kitteboss) - Tuesday, 18 December 2018, 09:01 GMT
Hi! I can confirm the issue. journalctl shows several entries of 'CTRL-EVENT-SCAN-FAILED ret=-22 retry=1'.
broadcom-wl-dkms 6.30.223.271-18
wpa_supplicant 1:2.7-1
Network controller: Broadcom Inc. and subsidiaries BCM4331 802.11a/b/g/n (rev 02)
Comment by Jakub Łabaj (byebye_pl) - Tuesday, 18 December 2018, 14:20 GMT
I have the same issue. Can connect to WiFi with wpa_supplicant 1:2.6-12, stops working with version 1:2.7-1.
Network card: Broadcom BCM4313, driver: broadcom-wl-dkms.
Comment by Luis Rodrigues Soares (luisonthekeyboard) - Tuesday, 01 January 2019, 17:17 GMT
Hi! I can also confirm the issue with the latest wpa_supplicant (1:2.7-1), same error messages as Chris.

I was able to work around it by *not* running it in daemon mode and by choosing the WEXT driver rather than the default nl80211 (`wpa_supplicant -i wlp4s0 -D wext -c /etc/wpa_supplicant-wlp4s0.conf`). However, I have to run this manually, can't run it from systemd. Ended up reverting to version 1:2.6-12.

Network Controller: Broadcom BCM4360 (14e4:43a0)
Kernel Driver: broadcom-wl 6.30.223.271-70


Hope this helps!
Comment by Gianluca Pettinello (gianluca.pettinello) - Tuesday, 01 January 2019, 21:25 GMT
I confirm the issue. Reverted to version 1:2.6-12
Comment by kiko loche (kikoloche) - Wednesday, 02 January 2019, 05:33 GMT
I confirm the bug too. Downgrading to 2.6 solves the problem.
Comment by Michael (Awesome_Donkey) - Wednesday, 02 January 2019, 11:38 GMT
I can confirm this as well, downgraded to 2.6 indeed solves the problem.
Comment by Kirill (SamuraiJack) - Wednesday, 02 January 2019, 16:32 GMT
Same here. Problem with 2.7-1 version.
Comment by Håvard Pettersson (haavard) - Wednesday, 02 January 2019, 16:38 GMT
Can we stop the "confirming the issue" comments that don't add any information and just vote for the issue instead?
Comment by Eric Blau (eblau) - Wednesday, 02 January 2019, 16:49 GMT
I'm seeing the same issue on my MacBook Pro 12,1 using the brcmfmac driver with wpa_supplicant 2.7 on linux-4.20.arch1-1. In my case, I get a kernel oops:

kernel: WARNING: CPU: 0 PID: 16169 at drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:5130 brcmf_cfg80211_set_pmk+0x50/0x70 [brcmfmac]
kernel: Modules linked in: brcmfmac ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo fuse iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c crc32c_generic br_netfilter bridge stp llc cmac bnep nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_hdmi sg crypto_user btusb btrtl btbcm btintel bluetooth asix usbnet joydev mii mousedev bcm5974 input_leds libphy ecdh_generic crc16 msr ofpart cmdlinepart intel_spi_platform intel_spi brcmutil intel_rapl spi_nor x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel mtd cfg80211 iTCO_wdt iTCO_vendor_support i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm i2c_algo_bit drm_kms_helper drm snd_hda_codec_cirrus snd_hda_codec_generic snd_hda_intel snd_hda_codec applesmc irqbypass input_polldev intel_cstate snd_hda_core mmc_core intel_uncore snd_hwdep intel_rapl_perf snd_pcm thunderbolt mei_me pcspkr lpc_ich intel_gtt i2c_i801 intel_pch_thermal snd_timer
kernel: agpgart mei rfkill snd syscopyarea spi_pxa2xx_pci sysfillrect sysimgblt acpi_als fb_sys_fops soundcore kfifo_buf sbs evdev industrialio sbshc mac_hid spi_pxa2xx_platform ac apple_bl pcc_cpufreq facetimehd(OE) videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media ip_tables x_tables zfs(POE) zunicode(POE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) spl(OE) algif_skcipher af_alg hid_apple hid_generic usbhid hid dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ahci libahci libata scsi_mod aesni_intel xhci_pci aes_x86_64 crypto_simd xhci_hcd cryptd glue_helper [last unloaded: brcmfmac]
kernel: CPU: 0 PID: 16169 Comm: wpa_supplicant Tainted: P W OE 4.20.0-arch1-1-ARCH #1
kernel: Hardware name: Apple Inc. MacBookPro12,1/Mac-E43C1C25D4880AD6, BIOS MBP121.88Z.0177.B00.1806051659 06/05/2018
kernel: RIP: 0010:brcmf_cfg80211_set_pmk+0x50/0x70 [brcmfmac]
kernel: Code: 8b 83 c8 08 00 00 83 b8 80 07 00 00 02 75 1b 0f b6 55 08 80 fa 20 77 1c 48 8b 75 10 48 8d bb c0 08 00 00 5b 5d e9 80 fe ff ff <0f> 0b b8 ea ff ff ff 5b 5d c3 b8 de ff ff ff eb f6 66 66 2e 0f 1f
kernel: RSP: 0018:ffffaad283d0ba98 EFLAGS: 00010293
kernel: RAX: ffff9aa6ee816000 RBX: ffff9aa6ee811000 RCX: ffff9aa80a77c000
kernel: RDX: ffffffffc10b8b7d RSI: ffffffffc10ade80 RDI: 0000000000000002
kernel: RBP: ffffaad283d0bab0 R08: 00000000000000fe R09: ffff9aa80a77c000
kernel: R10: 0000000000000000 R11: ffffffff848f5e58 R12: ffff9aa6ee816050
kernel: R13: ffff9aa6ee811000 R14: ffff9aa76cc10000 R15: ffff9aa76cc10300
kernel: FS: 00007fcfeb90a480(0000) GS:ffff9aa826a00000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 000055d5ae8e5fe0 CR3: 0000000227530005 CR4: 00000000003606f0
kernel: Call Trace:
kernel: nl80211_set_pmk+0x178/0x270 [cfg80211]
kernel: genl_family_rcv_msg+0x1c4/0x3c0
kernel: ? sock_def_readable+0xe/0x80
kernel: ? __netlink_sendskb+0x3d/0x50
kernel: genl_rcv_msg+0x47/0x90
kernel: ? __kmalloc_node_track_caller+0x1ed/0x290
kernel: ? genl_family_rcv_msg+0x3c0/0x3c0
kernel: netlink_rcv_skb+0x4c/0x120
kernel: genl_rcv+0x24/0x40
kernel: netlink_unicast+0x196/0x240
kernel: netlink_sendmsg+0x1fd/0x3c0
kernel: sock_sendmsg+0x33/0x40
kernel: ___sys_sendmsg+0x295/0x2f0
kernel: ? dev_get_by_name_rcu+0x73/0x90
kernel: ? dev_ioctl+0x171/0x3d0
kernel: ? __check_object_size+0xa0/0x189
kernel: ? preempt_count_add+0x79/0xb0
kernel: ? __inode_wait_for_writeback+0x7f/0xf0
kernel: ? preempt_count_add+0x79/0xb0
kernel: ? _raw_spin_lock+0x13/0x30
kernel: ? _raw_spin_unlock+0x16/0x30
kernel: ? __dentry_kill+0x116/0x160
kernel: __sys_sendmsg+0x57/0xa0
kernel: do_syscall_64+0x5b/0x170
kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
kernel: RIP: 0033:0x7fcfebe41fd8
kernel: Code: 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8d 05 65 65 0c 00 8b 00 85 c0 75 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 41 54 41 89 d4 55
kernel: RSP: 002b:00007ffdff680c48 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
kernel: RAX: ffffffffffffffda RBX: 000055cd5d162040 RCX: 00007fcfebe41fd8
kernel: RDX: 0000000000000000 RSI: 00007ffdff680c80 RDI: 0000000000000005
kernel: RBP: 000055cd5d189110 R08: 0000000000000004 R09: 00007fcfebf04150
kernel: R10: 00007ffdff680d54 R11: 0000000000000246 R12: 000055cd5d161f50
kernel: R13: 00007ffdff680c80 R14: ffffffffffffffff R15: 0000000000000000
kernel: ---[ end trace 462c92ab814d0cda ]---


Looking through the kernel code where this oops is emitted, it seems that wpa_supplicant is trying to use 4-way handshake offload and it is not supported properly by the firmware:

commit 2526ff21aa77c205f72e8263335f20b7d7e636fc
Author: Arend van Spriel <arend.vanspriel@broadcom.com>
AuthorDate: Fri Jun 9 13:08:48 2017 +0100
Commit: Kalle Valo <kvalo@codeaurora.org>
CommitDate: Fri Jun 30 09:38:22 2017 +0300

brcmfmac: support 4-way handshake offloading for 802.1X

Adding callbacks for PMK provisioning. If firmware supports offloading
it is indicated to user-space that 802.1X offload is supported.

Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>


ChangeLog for wpa_supplicant:

2018-12-02 - v2.7
* added support for nl80211 to offload 4-way handshake into the driver

Comment by Tom Boshoven (TBoshoven) - Wednesday, 02 January 2019, 20:27 GMT
I am seeing the same error as you, Eric.
A wpa_supplicant downgrade back to 2.6-12 resolves the issue.

Should probably add my system specs: XPS 15 (9550), BCM43602, Linux 4.20.0-arch1-1-ARCH.
Comment by Max Sydorenko (SydMax) - Wednesday, 02 January 2019, 21:52 GMT
This bug is not Broadcom specific. I observe the same issue on Atheros AR9380 with completely opensorce (and firmware free) ath9k driver. Downgrade to 2.6 again resolves problem.
Comment by kiko loche (kikoloche) - Thursday, 03 January 2019, 00:45 GMT
When I scan wifi services using connmanctl, no access point are found, but the command "sudo iw dev wlan0 scan" works fine and I get connected.
Comment by Bartłomiej Piotrowski (Barthalion) - Thursday, 03 January 2019, 14:43 GMT
Please report it upstream, I don't own affected card to write meaningful bug report.

I pushed downgraded package to [testing].
Comment by Eric Blau (eblau) - Thursday, 03 January 2019, 15:32 GMT
I'd be happy to report the bug upstream. Any suggestions on where to go though? The upstream URL, README file, etc. don't have any pointers for where to report bugs. I guess I'll just post on the wpa_supplicant mailing list, but if you have other suggestions, please let me know.
Comment by Eric Blau (eblau) - Thursday, 03 January 2019, 16:32 GMT
I've reported the issue to the wpa_supplicant mailing list but they believe this is a driver issue, so I've reported it to linux-wireless as well.
Comment by loqs (loqs) - Thursday, 03 January 2019, 21:17 GMT
Links to the mailing list discussions.
http://lists.infradead.org/pipermail/hostap/2019-January/039197.html
https://lore.kernel.org/linux-wireless/CADU241NrgYUq+eEyaNXteTA+KkPgcLXRHraR9y1OZm2bYY7U3g%40mail.gmail.com/
Comment by Luca Bacci (lb90) - Monday, 07 January 2019, 17:39 GMT
Same issue here
Comment by Gradyn Wursten (GNUGradyn) - Thursday, 10 January 2019, 16:50 GMT
Same issue here, BCM4331 on a Macbook pro 9,2 (mid 2012), downgrading wpa_supplicant to 1:2.6-12 did not solve the problem
Comment by Patrick O'Sullivan (patosullivan) - Tuesday, 15 January 2019, 17:28 GMT
I'm having the same issue on a Macbook Pro 11,1, BCM4360, broadcom-wl driver.

Downgrading did solve the problem.
Comment by Csaba Henk (csheemea) - Wednesday, 16 January 2019, 14:08 GMT
I met this issue on a Macbook Air, with BCM4360 chip and broadcom-wl. The workaround I'm using with success is to add '-Dwext' to the wpa_supplicant command line.
Comment by Zane Mingee (breakingmatter) - Wednesday, 16 January 2019, 18:34 GMT
Just wanted to confirm with my specific hardware details. A downgrade to wpa_supplicant v2.6 _does work_ for my hardware configuration.

Macbook Pro Retina Late 2013 15"
Model: ME294LL/A | MacbookPro11,3 | A1398 | 2745
URL: https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.3-15-dual-graphics-late-2013-retina-display-specs.html
WLAN Card: BCM4360
Driver: broadcom-wl-dkms v6.30.223.271-18
Affected Package: wpa_supplicant v2.7
Last confirmed working package: wpa_supplicant v2.6

Comment by Bartłomiej Piotrowski (Barthalion) - Wednesday, 16 January 2019, 20:19 GMT
I hope everyone saying "same here" realize that wpa_supplicant has been downgraded to 2.6 almost a week ago. It's not a packaging issue, Eric has reported it to both linux-wireless and hostapd maintainers, so that's about it unless someone wants to deep dive into the code of both.

Loading...