From nobody Mon Sep 06 15:41:13 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4273E17C0B69 for ; Mon, 6 Sep 2021 15:41:17 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3CL50ctFz4g92 for ; Mon, 6 Sep 2021 15:41:17 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4002a.ext.cloudfilter.net ([10.228.9.250]) by cmsmtp with ESMTP id NDc6ms7egps7PNGkGmoMlI; Mon, 06 Sep 2021 15:41:16 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NGkEmjUS0xCNkNGkFmKbNy; Mon, 06 Sep 2021 15:41:16 +0000 X-Authority-Analysis: v=2.4 cv=Xe/qcK15 c=1 sm=1 tr=0 ts=6136369c a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=QCccru2TAAAA:8 a=JAf30KXuAAAA:8 a=s1G7sxBSAAAA:20 a=QyJNKcYFpOw-pVCj0cAA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 a=rCjsK_HQOcgUb9vb-KUg:22 a=GEL62FyrTCmHtEug2d3R:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A44C442C; Mon, 6 Sep 2021 08:41:13 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186FfDRR024955; Mon, 6 Sep 2021 08:41:13 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061541.186FfDRR024955@slippy.cwsent.com> X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Idwer Vollering cc: Cy Schubert , "Oleg V. Nauman" , current@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: References: <2838567.hHqAuc6tWs@sigill.theweb.org.ua> <202109060550.1865oLlJ013110@slippy.cwsent.com> <202109061323.186DNLMQ010404@slippy.cwsent.com> Comments: In-reply-to Idwer Vollering message dated "Mon, 06 Sep 2021 16:50:18 +0200." List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Sep 2021 08:41:13 -0700 X-CMAE-Envelope: MS4xfK/WZk6a5KbPwMTO2UTE5oBeYd99Wep+Nu4GkcV9nffFRbf3A6vuJ5rFZRYt8Rf7OKChDAtX4j2RZD/WAD2Wxhy9fd7Wn5aV1UYSQjW4inT+ydbdBsDt 856zRCqoDLKuR3PbddVOXuEKNXa4HSTHtex1Um0tGO44tEWW7BVU6y9HAwtjfmUv4JPc7eZC5lTiLNcaOzGuB5fj638/cRV15hrKm6TSNL7GKBWce8o3MlIV Zm+lzAvYQ1GdpSlqPgazBA== X-Rspamd-Queue-Id: 4H3CL50ctFz4g92 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N I changed mine to be the same as yours. I can connect. (I use iwn(4) and ath(4) here.) Do you reboot every time you test or simply this? service netif stop wlan0 service netif start wlan0 If simply above, does a reboot have it work again? The reason I ask is, I discovered, today, a quirk in 14-CURRENT, regardless of the wpa_supplicant installed. It will always associate following a reboot however when running the above two commands to stop and start wlan0 I can reproduce your problem. The workaround for now is when running the above two commands to also ifconfig wlan0 down; ifconfig wlan0 up. Can you try ifconfig wlan0 down; ifconfig wlan0 up after stopping/starting wlan0? You may need to wait 2-3 seconds between down and up. If this occurs at boot, try the ifconfig down and up anyway (to help narrow down the problem). -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org The need of the many outweighs the greed of the few. In message , Idwer Vollering writes: > There's no core dump in /, wpa_supplicant connects to 802.11b/g/n > (there's no way to lock this, instead of having a mix of standards) on > 2,4GHz. > > /etc/wpa_supplicant.conf: > network={ > ssid="some ssid" > scan_ssid=1 > key_mgmt=WPA-PSK > psk="some key" > } > > Op ma 6 sep. 2021 om 15:23 schreef Cy Schubert : > > > > In message c > > om> > > , Idwer Vollering writes: > > > Op ma 6 sep. 2021 om 07:53 schreef Cy Schubert >: > > > > > > > > In message <2838567.hHqAuc6tWs@sigill.theweb.org.ua>, "Oleg V. Nauman" > > > > writes: > > > > > On 2021 M09 5, Sun 15:52:50 EEST David Wolfskill wrote: > > > > > > Sorry I hadn't noticed this yesterday (so I could have repported it > > > > > > then), but after updating the "head" slice of my laptopp from: > > > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #340 > > > > > > main-n249128-a0c64a443e4c: Fri Sep 3 04:06:12 PDT 2021 > > > > > > root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CA > NARY > > > > > > amd64 1400032 1400032 > > > > > > > > > > > > to: > > > > > > > > > > > > FreeBSD g1-51.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #341 > > > > > > main-n249146-cb5c07649aa0: Sat Sep 4 04:28:27 PDT 2021 > > > > > > root@g1-51.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CA > NARY > > > > > > amd64 1400032 1400032 > > > > > > > > > > > > I find that while the em0 NIC still works, wlan0 (iwn(4) HW) does n > ot: > > > > > > the WLAN LED doesn't light up. > > > > > > > > > > I am also experiencing issues with wlan after my current update to > > > > > 1f7a6325fe1b. I have checked ath(4) , run(4), rtwn(4) and all of them > > > > > demonstrating the same behavior - wlan can not associate. > > > > > You can mitigate it by using security/wpa_supplicant from ports as re > plac > > > emen > > > > > t > > > > > of wpa_supplicant in base. > > > > > > > > > > ..... > > > > > > > > > > > > I note that exactly the same hardware works OK in stable/12 and sta > ble/ > > > 13. > > > > > > > > > > > > Peace, > > > > > > david > > > > > > > > > > > > > Can you grep wpa_supplicant in /var/log/messages? This will give us a c > lue. > > > > > > wpa_supplicant stops in wpa_driver_bsd_scan() - > > > https://github.com/freebsd/freebsd-src/blob/bd452dcbede69b1862c769f244948 > f94b > > > 86448b5/contrib/wpa/src/drivers/driver_bsd.c#L1315 > > > > > > Here's some selected output from /var/log/messages. > > > > > > Before (built from commit a0c64a443e4cae67a5eea3a61a47d746866de3ee): > > > > > > Sep 6 13:29:40 wpa_supplicant[45348]: Successfully > > > initialized wpa_supplicant > > > Sep 6 13:29:40 wpa_supplicant[45348]: ioctl[SIOCS80211, > > > op=20, val=0, arg_len=7]: Invalid argument > > > Sep 6 13:29:40 syslogd: last message repeated 1 times > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Trying to > > > associate with (SSID='' freq=2447 MHz) > > > Sep 6 13:29:46 wpa_supplicant[45349]: Failed to add > > > supported operating classes IE > > > Sep 6 13:29:46 kernel: wlan1: link state changed to UP > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: Associated with > > > > > > > Sep 6 13:29:46 dhclient[45401]: send_packet: No buffer > > > space available > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: WPA: Key > > > negotiation completed with [PTK=CCMP GTK=CCMP] > > > Sep 6 13:29:46 wpa_supplicant[45349]: wlan1: > > > CTRL-EVENT-CONNECTED - Connection to completed [id=0 id_str=] > > > > > > After (built from main): > > > > > > Sep 6 12:19:50 wpa_supplicant[1236]: Successfully > > > initialized wpa_supplicant > > > Sep 6 12:19:50 kernel: wlan1: Ethernet address: > > > Sep 6 12:19:50 wpa_supplicant[1236]: ioctl[SIOCS80211, > > > op=20, val=0, arg_len=7]: Invalid argument > > > Sep 6 12:19:50 syslogd: last message repeated 1 times > > > Sep 6 12:19:50 wpa_supplicant[1237]: wlan1: > > > CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 > > > > Is there a wpa_supplicant.core dump in / ? > > > > Can you also send me a sanitized copy of wpa_supplicant.conf, please? I'm > > interested in the lines proto=, key_mgmt=, pairwise=, group=, eap=, and > > phase2=. You may not be using eap= or phase2=, which is fine. I'd like to > > see if there are any differences from what was tested. Though, looking at > > your outputs above you're probably using something like: > > > > proto=RSN WPA > > key_mgmt=WPA-PSK > > pairwise=CCMP > > group=CCMP > > > > Is this correct? > > > > If you try ports/securitiy/wpa_supplicant-devel (same codebase as in > > 14-CURRENT), does it work? (ports/security/wpa_supplicant is the old 2.9 > > codebase.) > > > > What is your AP set for? 802.11g, 802.11n, 802.11ac? > > > > > > -- > > Cheers, > > Cy Schubert > > FreeBSD UNIX: Web: https://FreeBSD.org > > NTP: Web: https://nwtime.org > > > > The need of the many outweighs the greed of the few. > > > >