Re: TKIP support for LinuxKPI/iwlwifi in main

On Mon, 28 Apr 2025, Kevin Oberman wrote:

> On Wed, Apr 23, 2025 at 11:42 AM Bjoern A. Zeeb <bz@freebsd.org> wrote:
>
>> XB!
>>
>> Hello everyone,
>>
>> I cmmitted TKIP support for LinuxKPI to main (will MFC in a few days).
>> The needed net80211 change went in as well (I think yesterday?).
>>
>> If you want to try it you have to enable it in loader.conf setting:
>>         compat.linuxkpi.80211.tkip=1
>>
>> The reason for this is that I belive that rtw88/rtw89 would need further
>> support in mac80211 and I don't want to break them currently.
>> Furthermore I don't want people to encourage using it anymore if
>> avoidable.
>>
>> I could only test on legacy (11g/11a) as (a) I had to force TKIP on on
>> my APs and (b) if TKIP was used I was not allowed to associate with HT/VHT
>> anymore.  I hope the APs/Routers for the people waiting for this will
>> allow them at least on HT (or VHT) depending on age.
>>
>> I made sure that at least the Gtk (Group Temporal Key) update worked for
>> me.
>>
>> Please report back how this goes!
>>
>> Lots of joy,
>> Bjoern
>
>
> Thanks for getting this out. Seems to be working fine for my Alder Lake
> iwlwifi.
>
> That said, enabling TKIP did trigger some unexpected changes... unexpected,
> but not bad.
..
> As you can see, I now have mode 11ng. Ths appeared when I restarted with
> compat.linuxkpi.80211.tkip=1 buth without enabling hardware crypto. If I
> look at the sysctl, it
> shows '0'.

I am really confused.  Something else is going on as the tkip tunable
does not do anything if hw_crypto is 0.


> In any case, I will be moving tomorrow and will be on Comcast with a newer
> router. I assume

Have a save move and let us know once you are back online how things
are.

/bz

-- 
Bjoern A. Zeeb                                                     r15:7