From nobody Tue Sep 07 08:13:23 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 053F91799453 for ; Tue, 7 Sep 2021 08:13:33 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4H3dM014mvz3qlN for ; Tue, 7 Sep 2021 08:13:32 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-d24b235c.06-431-73746f70.bbcust.telenor.se ([92.35.75.210] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1mNWEN-000O8I-Vl; Tue, 07 Sep 2021 10:13:23 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alvermark.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=P4cIrCY72omfJMVwvlMLbiha2Jm6wq3NOJbGhO6DFY4=; b=YRG/LYmF2O6NUvSZzXgjS/T+81 QRaQ9GKw9VOlNe/ElwxaHF/OLy9j0h7jYQvIyyRWsls5WtDj38jxKhJ0kt1BLc6/QOpKbxwcVrTPw GFwZpp8xWSBDF0H95mbWeLmw3+KimMdYYEFCZK9E8V9ffBB5+6Zdl9eql3pLBNlM7r2yue5iy5DQf EkT8Quh6En0lUMqS2tSh0M9w7OHom/2p6Y4LT0vxsofis770mz5GwJs1lzHJyMcjI9y0swLo0mJ9K HRp05CWAeLVMuph+xhbWOCZnUD4Uui18xkTax1dNR8USbFpLMs0TzrchfoWiuHhgdDLRR9XF2GMxm obDcJhig==; Received: from 92-244-0-135.customers.ownit.se ([92.244.0.135] helo=[192.168.1.221]) by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1mNWEN-000C6Z-GZ; Tue, 07 Sep 2021 10:13:23 +0200 Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 To: Cy Schubert Cc: current@freebsd.org References: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> <202109061731.186HVXr5004438@slippy.cwsent.com> <2780735.SSXfckUlLJ@sigill.theweb.org.ua> <202109061821.186ILt9b005261@slippy.cwsent.com> From: Jakob Alvermark Message-ID: <88f22f7e-3f5c-7e97-4ec2-aa43dd2f6a11@alvermark.net> Date: Tue, 7 Sep 2021 10:13:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 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 In-Reply-To: <202109061821.186ILt9b005261@slippy.cwsent.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 4H3dM014mvz3qlN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=alvermark.net header.s=x header.b="YRG/LYmF"; dmarc=none; spf=pass (mx1.freebsd.org: domain of jakob@alvermark.net designates 185.34.136.138 as permitted sender) smtp.mailfrom=jakob@alvermark.net X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[alvermark.net:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-0.998]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/23, country:IT]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 9/6/21 8:21 PM, Cy Schubert wrote: > 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. > Hi, I have the same. wlan0 does not associate after boot. (This is with iwm, AC 9260) My workaround is simply 'ifconfig wlan0 up'. After a few seconds wpa_supplicant associates and another few secods later I have a DHCP IP address. Jakob