Date: Tue, 22 Mar 2022 15:33:20 -0400 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: "Bjoern A. Zeeb" <bz@FreeBSD.org> Cc: freebsd-wireless@freebsd.org Subject: Re: iwlwifi/LinuxKPI 802.11 update Message-ID: <20220322193320.6nfr2uku46fxejnw@mutt-hbsd> In-Reply-To: <alpine.BSF.2.00.2203221855270.68830@ai.fobar.qr> References: <alpine.BSF.2.00.2203221855270.68830@ai.fobar.qr>
next in thread | previous in thread | raw e-mail | index | archive | help
--cbgfmot457gslzq4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 22, 2022 at 07:30:13PM +0000, Bjoern A. Zeeb wrote: > Hi, >=20 > as you may have noticed I've just pushed a few changes into main which > I hope will solve some of the problems people have been seeing with > stability. >=20 > Everyone running HEAD: it would be great to see if these commits help yo= u. > There are still more rough edges to sort out and probably some cases > I could not test/reproduce but piling more up isn't helpful. >=20 > For eveyone on stable/13: I'll try to get all other changes (before > today) moerged to stable/13 and will merge these in 3-ish days as > well. You could always cherry-pick them manually yourself. Let me > know if you would want to and need help for that. >=20 >=20 > Things I noticed: >=20 > (a) if you think you "cannot connect" it might be that wpa_supplicant > managed to associate but not authorize. I have that once in a while. > Check your wpa_supplicant logs (possibly increase the log level). >=20 > Usually triggering a successful scan (I often have to try twice): > ifconfig wlan0 scan > ifconfig wlan0 scan > will then DTRT for me and on 2nd attempt authorizing will work. >=20 > If wpa_supplicant decided to disable the network temporary > (wpa_cli list_networks will tell) you can disable / enable > the network to unblock that as well. >=20 > (b) ifconfig wlanX down / up needs some state to clear as well > to work better. I'll look into that probably Thursday along > with hw_restart so that we can recover from firmware crashes > if general state got better now. >=20 >=20 > Bjoern Hey Bjoern, Thanks a lot for your hard work! A while ago (few months ago), we talked about issues relating to iwlwifi and lagg failover. Should I give lagg failover another try at this point? Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --cbgfmot457gslzq4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmI6JH0ACgkQ/y5nonf4 4fo58w//aPYAUSrBRKg6SpuL1fT7rGE+4FQmnEDwJ3sQEuyqxszjLZg8zrTys0on cWqOkwJWXh0lKd51aAchcK7AV/799DUyvptXySBy6TjUtVARBX4Wq63sEkfs+kM9 Ji0EjXdM44JgKafn2DVZXCSUJFLjfPXaaezYPq9BFNSKkQLdfiJHYAIav25QbpCI lMEhHl1bBRPdM8hL+Zpxhr1huwrrzC3viNTl+j6M5ahl3PYpDXbIHEulx39NAKlm UUmwRNQQ/EciUW4PNzoBEMeroDisEMR2BqSew/wKBmtfpU9UNxJdUp5K2lPLqZG3 r929+etkcWZo8LSC8pljH8CQGoE8riEpzQe6KaeEgVmJJUqmBqlmhL4SL0GgcqMD T+Z0dSST9yNaNDmkn1wPGjrL3+qOCjQAPd3MLlOq5mkYDpsBfSY7yu/KWRfJowiO 3gCSUxPXgUqem0OmrEiXSRhp1vqusCh8bcs6BBww/lCZxiljptGCpY7kevbp3LK3 c9KNCZtxNCv16iW3Pm3qXhnVwxcSLCdsCDQKOowz8oKwlxp2LXip/m8bShHKA+Gn 6gRq3mUMocWb2W6DI/lhzhzr57KNBONH+lk48K8JP85IpXpp1kgbhasS4YbtvLKJ G+66BLgmmv3GhciQy5/ryXaMhD3NEyzGsukiPaHkORg6a9vIXdc= =FxWV -----END PGP SIGNATURE----- --cbgfmot457gslzq4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220322193320.6nfr2uku46fxejnw>