From nobody Mon Mar 03 00:39:17 2025 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z5g1h48wGz59X59 for ; Mon, 03 Mar 2025 00:39:36 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z5g1g37qdz3W7l; Mon, 03 Mar 2025 00:39:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=YfnenYVl; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::112c as permitted sender) smtp.mailfrom=kob6558@gmail.com Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-6fd2fca1cebso23336327b3.0; Sun, 02 Mar 2025 16:39:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740962374; x=1741567174; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oz4GjhQEtxnP2WDHW2UKges248jQ18yprJRUuhpbQfs=; b=YfnenYVlqdow2RcGulXrGKWxTNJbhKENlLQlQA9n2SAOj3+ISyTfA7wRSOwUbg9Tua DTwlGiduXPB3Cp6u8jvcK1RUERiyDPu2LKbjl/WpiP2HEJtq5JUsCCFALBPzuQtXiUBA 48WabhZDh7LP7iLGTQY9k3VcjKO8NNmlXVER1/oXivKbAyEvSXfccubP+R1muxaI1Qzk n087macSSFAM4gpLr9xpkR0eo9WaYmQLuISX1j0fCKrhBxMGGnZ7reP+aY04I+PtsypY DPu33hVmFaOrr8dIElffdRdZ6s3xlrVrlEJMxf1rm88+4FXwVoOhSlQcpAN/5EIZbndK /Utw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740962374; x=1741567174; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oz4GjhQEtxnP2WDHW2UKges248jQ18yprJRUuhpbQfs=; b=jHxHUCt32f3eV0S0sttJLXjocG4svwcZxkWRGTuo9NuoKci37fHoQ13CsMro+sCh0U X5IUAvb8RxeSVb36kP5QP4ufMpdeMfJYG3FtH5lCGVNI37g7hdahVunT/+ZibuDksC9r XwnTD1Tw043zedwO0eCvk7u/0AmSU16kKwwx6hexJ1xlYFpBRy2qcf8NOj/d0feh++q7 rgaUN4WSZenn54ZNkjcpO/trGMvoyuGSg8HxOaqWOCOro0Rgk/C3sjJ2da8+Q6LKml// Qh7JH1miaL3bWebC+upykRqRMZXeqrJds1LspX4gYL8v+xpYPO+U8tvuVDVPczw8U8ru XQFA== X-Gm-Message-State: AOJu0Yxvy8Kbp0YXEhw4X2Y34zq5OGnZRxfy/s8WY1VCgmuqre58NmD7 Ohb+0HISSDqmO75dGNuJztnZFFYzCbyRUqtCeEXfKncS1/6NX68n6kir9zo/Nx6iBkUYWYcs6K0 ++ONNq7yS95pIp5BeEwEhYjRaZi71+m29 X-Gm-Gg: ASbGncvjzIIyUsOly1RKF2T0tLx42jGJEoM+3WxzN2kUR98wzW7WPqQvEqRQBlfYtz5 0lFPBFHqchl6/LLEhHKGcTEQcYRX0JTvjDbX+3l9Dkv/L+AMyYvFW4uYWatkUqUVwIWGM5zzr3G TwuhfpyczX4i3MhOjliEASm1irRpk= X-Google-Smtp-Source: AGHT+IEqFk1Ui3pOGkIkTR9FsBhHHKgOP8UspLW8xFtPDRvYPUFw8uuC9UxIgzMXsJTSqCPOjsXgRg7l24Aoj+rLyKU= X-Received: by 2002:a05:690c:4a0e:b0:6fb:1c5a:80fc with SMTP id 00721157ae682-6fd4a0c405amr154208127b3.26.1740962373742; Sun, 02 Mar 2025 16:39:33 -0800 (PST) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Sun, 2 Mar 2025 16:39:17 -0800 X-Gm-Features: AQ5f1JoyAx-9KUhNthvS4XQCgoPg9J2Bk8xShDmK-CCR-KneUJ1XsSuzHd-mLRI Message-ID: Subject: Re: iwlwifi / rtw88 / rtw89 hw crypto request for test (precon for HT/VHT) To: "Bjoern A. Zeeb" Cc: FreeBSD wireless mailing list Content-Type: multipart/alternative; boundary="000000000000dab9a9062f656346" X-Spamd-Result: default: False [-3.64 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.99)[-0.986]; NEURAL_HAM_MEDIUM(-0.95)[-0.953]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112c:from] X-Rspamd-Queue-Id: 4Z5g1g37qdz3W7l X-Spamd-Bar: --- --000000000000dab9a9062f656346 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Feb 17, 2025 at 8:01=E2=80=AFPM Bjoern A. Zeeb wro= te: > Hi, > > with [1] I added HW_CRYPTO support to the build for all LinuxKPI based > drivers. This is a pre-condition to make HT/VHT work with drivers/fw > which support, e.g., A-MPDU offloading -- basically almost everything > modern. > > I will very likely MFC it at the end of the week if I didn't put in any > last minute bugs. > > As the commit message says it currently only supports CCMP. If you > still do WEP or TKIP please let me know and I'll add it to the list > though I'll then likely want your help to test (patches) as well. > > As also mentioned in the commit message I saw one specific panic in the > past which I no longer can reproduce. I am sure there's some other edge > cases on more devices so I need your help to test. > > While the code is compiled in now it is disabled behind a tunable until > there is sufficient feedback for iwlwifi, rtw88 and rtw89 that it works. > Once that happens I'll flip the default for the tunable at least to on > and eventually remove it alltogether and we can move to the next steps > of testing which is hopefully fully merged to git by then. > > So if you want some HT/VHT to work with at least modern iwlwifi, and then > also older iwlwifi, rtw88 and rtw89 in th enext steps please help testing > and report back the next days. > > To turn the code on add the following line to laoder.conf: > compat.linuxkpi.80211.hw_crypto=3D1 > > At runtime you can check the state by using: > sysctl compat.linuxkpi.80211.hw_crypto > > Also if you have any problems, then you can easily remove that line (or > unset it from loader) and boot with the support turned on. > > If you reply to this thread or me (positive or negative feedback), please > add the pciconf -l line for your wifi card so we known about the chipset. > > > Lots of joy, > Bjoern > > [1] > https://cgit.FreeBSD.org/src/commit/?id=3D11db70b6057e41b259dc2245cd893d5= b19179fcc > > -- > Bjoern A. Zeeb r15:7 > > I was excited to see that it looked like 802.11n was on the way! Tried step one, enabling 802.11 crypto, and had no luck at all. I know my AX211 supports CCMP, but attempting to boot gets: wlan0: link state changed to UP iwlwifi0: _lkpi_iv_key_set: CIPHER SUITE 0xfac02 (TKIP) not supported wlan0: link state changed to DOWN Why don't I see any attempt to do CCMP? Am I looking at an issue with the Arris WiFi provided by my carrier (Frontier)? I can't find any reference to encryption in the DHCP configuration. Mine is very basic PSK: network=3D{ ssid=3D"My BSS" psk=3D"My key" priority=3D5 } After several tries at getting an address, it gives up and the system crashed. I have the text dump and will attach the crash message. Also have the full dmesg, if they are of use. I probably am simply missing something. Thanks! I enabled it is loader.conf, but the reboot failed to connect and then crashed. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000dab9a9062f656346 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Feb 17, 2025 at 8:01=E2= =80=AFPM Bjoern A. Zeeb <bz@freebsd.or= g> wrote:
Hi,

with [1] I added HW_CRYPTO support to the build for all LinuxKPI based
drivers.=C2=A0 This is a pre-condition to make HT/VHT work with drivers/fw<= br> which support, e.g., A-MPDU offloading -- basically almost everything
modern.

I will very likely MFC it at the end of the week if I didn't put in any=
last minute bugs.

As the commit message says it currently only supports CCMP.=C2=A0 If you still do WEP or TKIP please let me know and I'll add it to the list
though I'll then likely want your help to test (patches) as well.

As also mentioned in the commit message I saw one specific panic in the
past which I no longer can reproduce.=C2=A0 I am sure there's some othe= r edge
cases on more devices so I need your help to test.

While the code is compiled in now it is disabled behind a tunable until
there is sufficient feedback for iwlwifi, rtw88 and rtw89 that it works. Once that happens I'll flip the default for the tunable at least to on<= br> and eventually remove it alltogether and we can move to the next steps
of testing which is hopefully fully merged to git by then.

So if you want some HT/VHT to work with at least modern iwlwifi, and then also older iwlwifi, rtw88 and rtw89 in th enext steps please help testing and report back the next days.

To turn the code on add the following line to laoder.conf:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 compat.linuxkpi.80211.hw_crypto=3D1

At runtime you can check the state by using:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sysctl compat.linuxkpi.80211.hw_crypto

Also if you have any problems, then you can easily remove that line (or
unset it from loader) and boot with the support turned on.

If you reply to this thread or me (positive or negative feedback), please add the pciconf -l line for your wifi card so we known about the chipset.

Lots of joy,
Bjoern

[1] https://cgit.F= reeBSD.org/src/commit/?id=3D11db70b6057e41b259dc2245cd893d5b19179fcc
--
Bjoern A. Zeeb=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15:7

I was excited to see that it looked like = 802.11n was on the way! Tried step one, enabling 802.11 crypto, and had no = luck at all. I know my AX211 supports CCMP, but attempting to boot gets:
wlan0: link state changed to UP
iwlwifi0: _lkpi_iv_key_set:= CIPHER SUITE 0xfac02 (TKIP) not supported
wlan0: link state changed to = DOWN

Why don't I see any attempt to = do CCMP? Am I looking at an issue with the Arris WiFi provided by my carrie= r (Frontier)? I can't find any reference to encryption in the DHCP conf= iguration. Mine is very basic PSK:
network=3D{
=C2=A0 ssi= d=3D"My BSS"
=C2=A0 psk=3D"My key"
=C2=A0 priorit= y=3D5
}


After several tries a= t getting an address, it gives up and the system crashed. I have the text d= ump and will attach the crash message. Also have the full dmesg, if they ar= e of use. I probably am simply missing something.

=
Thanks!

I enabled it is loader= .conf, but the reboot failed to connect and then crashed.


--
Kevin Oberman, Part time kid h= erder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Finge= rprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000dab9a9062f656346--