On Wed, 5 Feb 2025, Nico Sonack wrote:
Hello wireless people,
pardon me for the previous mail, I didn't have the necessary coffee
loaded to control my mail client ;-)
Anyways, I'm having difficulty getting the following setup to work:
# uname -a
FreeBSD ... 14.2-RELEASE FreeBSD 14.2-RELEASE #7
releng-patched/14.2-n269511-85e6ff33f892: Tue Jan 14 08:40:39 UTC 2025
root@bork:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-RACK amd64
# pciconf -lv
iwlwifi0@pci0:0:20:3: class=0x028000 rev=0x01 hdr=0x00 vendor=0x8086
device=0x51f1 subvendor=0x8086 subdevice=0x4090
vendor = 'Intel Corporation'
device = 'Raptor Lake PCH CNVi WiFi'
class = network
# dmesg | grep iwlwifi
iwlwifi0: <iwlwifi> mem 0x60531a4000-0x60531a7fff at device 20.3 on pci0
iwlwifi0: Detected crf-id 0x401410, cnv-id 0x80400 wfpm id 0x80000020
iwlwifi0: PCI dev 51f1/4090, rev=0x370, rfid=0x2010d000
iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0-83.ucode'
iwlwifi0: api flags index 2 larger than supported by driver
iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
iwlwifi0: loaded firmware version 83.e8f84e98.0 so-a0-gf-a0-83.ucode op_mode
iwlmvm
iwlwifi0: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370
iwlwifi0: WRT: Invalid buffer destination: 0
iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20
iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
iwlwifi0: WFPM_AUTH_KEY_0: 0x90
iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
iwlwifi0: RFIm is deactivated, reason = 4
iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0.pnvm'
WPA2 with a simple PSK seems to work fine, however I'm getting
failures when trying to connect with WPA enterprise with EAP-PEAP.
The wpa_supplicant.conf roughly contains:
pmf=2
network={
ssid="secret-ssid"
proto=RSN
key_mgmt=WPA-EAP-SHA256
pairwise=CCMP
group=CCMP
eap=PEAP
identity="bofh"
password="hunter2"
ca_cert="cert-goes-here.cer"
phase2="auth=MSCHAPV2"
ieee80211w=2
}
Now, when bringing the interface up everything seems to work fine,
EAP-PEAP succeeds. Then I get the following failure in the
wpa_supplicant:
wpa_supplicant[36003]: bsd_set_key: unknown alg=4
alg=4 would be WPA_ALG_BIP_CMAC_128 which is in in the file:
384 case WPA_ALG_BIP_CMAC_128:
385 wk.ik_type = IEEE80211_CIPHER_BIP_CMAC_128;
386 break;
387 default:
so I am a bit confused as to why it would log the default case below.
Oh, this is main where Adrian has added the placeholders. Let me check
stable/14. Yepp, there they are not avail and the deault printf is expected.
Now I should og and see if I accidently advertise these as avail in
iwlwifi and it doesn't seem so.
So the question is where does this come from for you?
Can you actually add proto=WPA2 as indicated in the Subject line and see what
happens?
wpa_supplicant[36003]: wlan0: WPA: Failed to configure IGTK to the driver
wpa_supplicant[36003]: wlan0: RSN: Failed to configure IGTK
wpa_supplicant[36003]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=**:**:**:**:**:** reason=1 locally_generated=1
wpa_supplicant[36003]: wlan0: Added BSSID **:**:**:**:**:** into ignore
list, ignoring for 10 seconds
wpa_supplicant[36003]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid
argument
kernel: wlan0: link state changed to DOWN
wpa_supplicant[36003]: wlan0: Removed BSSID **:**:**:**:**:** from ignore
list (clear)
dhclient[54738]: send_packet: Network is down
I'm a bit at a loss here since I have gotten this kind of setup to
work before - though with iwm and not the linuxkpi/iwlwifi driver.
Note that iwm seems to not be supported with this chipset (unless I'm totally
wrong here).
No. iwm doesn't support that card anymore but that's likely not related
to this issue anyway.
--
Bjoern A. Zeeb r15:7
