From nobody Mon Sep 06 18:21:55 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 F18D517ACE2E for ; Mon, 6 Sep 2021 18:22:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (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 4H3GvT5v8Cz4nhX for ; Mon, 6 Sep 2021 18:21:57 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from shw-obgw-4004a.ext.cloudfilter.net ([10.228.9.227]) by cmsmtp with ESMTP id NH54mArnyczbLNJFlmKUw2; Mon, 06 Sep 2021 18:21:57 +0000 Received: from spqr.komquats.com ([70.66.148.124]) by cmsmtp with ESMTPA id NJFkm5PyWdCHGNJFlmoQYZ; Mon, 06 Sep 2021 18:21:57 +0000 X-Authority-Analysis: v=2.4 cv=SdyUytdu c=1 sm=1 tr=0 ts=61365c45 a=Cwc3rblV8FOMdVN/wOAqyQ==:117 a=Cwc3rblV8FOMdVN/wOAqyQ==:17 a=kj9zAlcOel0A:10 a=7QKq2e-ADPsA:10 a=QCccru2TAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=EkcXrb_YAAAA:8 a=2lwzVihPj1q7mMlt1dkA:9 a=CjuIK1q_8ugA:10 a=rCjsK_HQOcgUb9vb-KUg:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A8C0612C; Mon, 6 Sep 2021 11:21:55 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.16.1/8.16.1) with ESMTP id 186ILt9b005261; Mon, 6 Sep 2021 11:21:55 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <202109061821.186ILt9b005261@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: "Oleg V. Nauman" cc: Cy Schubert , current@freebsd.org, Idwer Vollering , phlip@freebsd.org Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 In-reply-to: <2780735.SSXfckUlLJ@sigill.theweb.org.ua> References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> Comments: In-reply-to "Oleg V. Nauman" message dated "Mon, 06 Sep 2021 20:49:01 +0300." 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 11:21:55 -0700 X-CMAE-Envelope: MS4xfLg8DfEEddHQo+qSpP8KV+JrVX2dKDWGJvKxoojHEuGdvlxksEIzf7lbdp9/pBA1G8trz3q3bD2B1kRx0noIkzxpJLe8+gIeyUyptB3qIDLSlWDKbajZ yKhHoKohCQC9J82mY/dZ7HdC276o0aVM4UnhE1k6vMeuop9ebXTOndAElSPZm6n9tkDCOEN/9TnAVSrhKOIA0cnxWUTfsLD2B9rjsiAsyKQTJC41HaMoR6CQ gl24JhWPj4dswgJxYYfmUXezNEThW7lGs1putc04iwI2RKI/CpFEf7rVwwPnNbYt X-Rspamd-Queue-Id: 4H3GvT5v8Cz4nhX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N In message <2780735.SSXfckUlLJ@sigill.theweb.org.ua>, "Oleg V. Nauman" writes: > On 2021 M09 6, Mon 20:31:33 EEST Cy Schubert wrote: > > One last favour to ask, can you try this with the wpa_supplicant-devel > > port, please? I'm trying to narrow down if this is related to the options > > in usr.sbin/wpa/Makefile.inc or an upstream problem. If this behaves the > > same using wpa_supplicant-devel, this tells me to look at the code instead > > of Makefiles. > > > > I can reproduce the service netif restart problem using the old > > wpa_supplicant 2.9, so at least here there is no change in behaviour. > > Though on my sandbox machine the ifconfig dow/up is not required -- though > > even the older wpa_supplicant 2.9 behaves the same on my laptop, (no > > regression experienced here). > > > > To help point to either Makefile.inc or contrib/wpa, can you please try the > > wpa_supplicant-devel port. This will tell me where to look next. > > I can confirm that wpa_supplicant from security/wpa_supplicant-devel port > demonstrating the same behavior as wpa_supplicant from base - "ifconfig wlan0 > > down ; sleep 5 ; ifconfig wlan0 up" mitigate wlan association issue. Thank you. This is an issue that I'll need to chase down with our upstream. In the mean time while work on this/bring it to upstream's attention this should circumvent the issue: diff --git a/libexec/rc/rc.d/wpa_supplicant b/libexec/rc/rc.d/wpa_supplicant index 8a86fec90e4d..cfe5f1ab27c6 100755 --- a/libexec/rc/rc.d/wpa_supplicant +++ b/libexec/rc/rc.d/wpa_supplicant @@ -12,6 +12,7 @@ name="wpa_supplicant" desc="WPA/802.11i Supplicant for wireless network devices" +start_postcmd="wpa_poststart" rcvar= ifn="$2" @@ -27,6 +28,12 @@ is_ndis_interface() esac } +wpa_poststart() { + ifconfig ${ifn} down + sleep 3 + ifconfig ${ifn} up +} + if is_wired_interface ${ifn} ; then driver="wired" elif is_ndis_interface ${ifn} ; then I'll have more questions later (need to start working on another job) but I'd like to learn more about your configuration to understand why it works at boot for myself and phlip@ and not for you and the others here on -current who have experienced the same issue. Understanding what triggers this will go a long way to resolving it. (cc'd philip@) BTW, my laptop is configured so that wlan0 (iwn0) and bge0 are members of lagg0. Whereas on my sandbox wlan0 (ath0) is used directly. -- 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.