Date: Fri, 29 Aug 2025 19:57:52 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: ltning-freebsd-wireless@anduin.net Cc: freebsd-wireless@freebsd.org Subject: Re: iwlwifi: Really hard to connect to networks Message-ID: <n1708583-1pr4-r615-op8n-5413r65983o4@SerrOFQ.bet> In-Reply-To: <13f405a6-e73c-4872-86f3-f74e97dc0969@anduin.net>
index | next in thread | previous in thread | raw e-mail
On Sun, 24 Aug 2025, ltning-freebsd-wireless@anduin.net wrote: Hi, I waited a few days replying as I wanted to have some changes in the tree first. > I think I mentioned this in a post a couple of months ago as well, but since > nothing's changed, here I go again: > > While iwlwifi seems quite stable and fast once I'm connected to a network, > getting there is a bit hard. Basically what happens when I try to connect is > that repeated "ifconfig wlan0" invocations (with no options) show it > associating and disconnection many, many times (dozens) before finally > "settling". During this time, there *is* clearly a working connection because > at times it will acquire an IP address via DHCP, and some applications may > (very) briefly be able to speak to the internet. Yes, you can see the interface UP/DOWN. I can see "no beacon heard". There is a slightly enhanced message with some more information in main now. There's also changes related to that in main as of the last days (we do count these beacons, we take some information for updates from elsewhere [which should not make the difference], I reworked the filter updates, .. Depending on whether it still happens you may want to keep options IEEE80211_DEBUG # enable debug msgs in your kernel config (assuming you are not runnign GENERIC with all debugging on) so we could go and have a look enabling some more logging. > Also confusing is that even though I've told wpa_supplicant.conf to ignore my > 2.4GHz BSSIDs *and* given an explicit frequency, it sometimes ends up > connecting to that. I can see it did. It's hard to say without knowing the wpa_supplicant.conf if it really should not. Did you actually disable the network entry or how do you try to prevent it from trying to use it? > There seems to be both firmware crashes and other weirdness going on. I've Yes, I saw that too. If it happens again after the update wee need to see. Could be from changing bands; I need to go and have a look about that. If it was crypto related there's also a catch for that in main. Let us know how it goes (or not) in a main from today or a later time. Lots of health, Bjoern -- Bjoern A. Zeeb r15:7home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?n1708583-1pr4-r615-op8n-5413r65983o4>