Date: Mon, 06 Sep 2021 19:26:34 +0300 From: "Oleg V. Nauman" <oleg@theweb.org.ua> To: Cy Schubert <Cy.Schubert@cschubert.com>, current@freebsd.org Cc: Idwer Vollering <vidwer@gmail.com> Subject: Re: wlan0 no longer functional after n249128-a0c64a443e4c -> n249146-cb5c07649aa0 Message-ID: <3000346.ZmR5Pbtf01@sigill.theweb.org.ua> In-Reply-To: <202109061541.186FfDRR024955@slippy.cwsent.com> References: <YTS9onwkB4Ojr4cG@albert.catwhisker.org> <CAPp9Or=L%2B-%2BTAD4c19cRGks5oEZ9UwPoOp%2BXq2OO9%2BCwaKt-4w@mail.gmail.com> <202109061541.186FfDRR024955@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021 M09 6, Mon 18:41:13 EEST Cy Schubert wrote: > I changed mine to be the same as yours. I can connect. (I use iwn(4) and > ath(4) here.) a ) regular reboot - wlan can not associate b ) service netif restart - wlan can not associate c ) service netif stop wlan0 ; service netif start wlan0 - wlan can not associate d ) ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up - wlan associated e ) regular reboot with ifconfig wlan0 down; sleep 15 ; ifconfig wlan0 up added to /etc/rc.local - wlan associated Thank you. > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3000346.ZmR5Pbtf01>