Re: iwlwifi: Really hard to connect to networks

From: <ltning-freebsd-wireless_at_anduin.net>
Date: Sat, 30 Aug 2025 13:24:47 UTC
On 8/29/25 21:57, Bjoern A. Zeeb wrote:
> On Sun, 24 Aug 2025, ltning-freebsd-wireless@anduin.net wrote:
> 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.

I'll rebuild soon with this option set, since I'm running 
GENERIC-NODEBUG right now.


>> 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?

I do this in wpa_supplicant.conf:

   network={
     ssid="Casa di Mau"
     scan_ssid=0
     psk="<foobar>"
     priority=5
     bssid_ignore=f0:9f:c2:03:c7:51 f0:9f:c2:ad:40:6e 98:ba:5f:d7:71:b2
     frequency=5240
   }

And in rc.conf:
   ifconfig_wlan0="WPA DHCP country NO regdomain ETSI chanlist 36-100"


> 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.

Attached dmesg from boot right now. The interface did not come up 
properly  until I did a "service netif restart wlan0" (not included in 
the dmesg).

Gotta run now, can collect more debug info later.. Hope this helps, though!

/Eirik