AX210 I am able to scan my wifi networks, but it won't connect to any ssid.

[AntonP8O]

Hello i have debian 12 with proxmox, and my AX210 won't connect to my ssid.

I'm not the only one who has encountered this problem, pls check proxmox forum
https://forum.proxmox.com/threads/proxmox-v8-0-and-intel-ax210.131902/
My diagnostic information
Motherboard: asrock B450M Pro4

dmesg | grep 'iwlwifi'
[    7.444932] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    7.447103] iwlwifi 0000:01:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
[    7.447124] iwlwifi 0000:01:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
[    7.478477] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
[    7.478987] iwlwifi 0000:01:00.0: loaded firmware version 86.fb5c9aeb.0 ty-a0-gf-a0-86.ucode op_mode iwlmvm
[    7.568818] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[    7.576760] iwlwifi 0000:01:00.0: WRT: Invalid buffer destination
[    7.729285] iwlwifi 0000:01:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    7.729323] iwlwifi 0000:01:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    7.729352] iwlwifi 0000:01:00.0: WFPM_AUTH_KEY_0: 0x90
[    7.729386] iwlwifi 0000:01:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[    7.730775] iwlwifi 0000:01:00.0: loaded PNVM version 35148b80
[    7.745905] iwlwifi 0000:01:00.0: Detected RF GF, rfid=0x10d000
[    7.815824] iwlwifi 0000:01:00.0: base HW address: 8c:f8:c5:ec:df:74
[    7.902268] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0

lspci -nnk

01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
        Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz [8086:0024]
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

journalctl -k -o short-precise --no-hostname -p warning..emerg -x

июл 28 08:52:55.824954 kernel: Speculative Return Stack Overflow: IBPB-extending microcode not applied!
июл 28 08:52:55.824960 kernel: Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
июл 28 08:52:55.844799 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
июл 28 08:52:55.844992 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
июл 28 08:52:55.845074 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
июл 28 08:52:55.845150 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
июл 28 08:52:55.845224 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
июл 28 08:52:55.845317 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
июл 28 08:52:55.845415 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
июл 28 08:52:55.845490 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
июл 28 08:52:55.845564 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
июл 28 08:52:55.845637 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
июл 28 08:52:55.852253 kernel: nvme nvme0: missing or invalid SUBNQN field.
июл 28 08:52:55.864425 kernel: spl: loading out-of-tree module taints kernel.
июл 28 08:52:55.869791 kernel: zfs: module license 'CDDL' taints kernel.
июл 28 08:52:55.869828 kernel: Disabling lock debugging due to kernel taint
июл 28 08:52:55.869839 kernel: zfs: module license taints kernel.
июл 28 08:52:56.371094 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
июл 28 08:52:56.371116 kernel: Bluetooth: hci0: sending frame failed (-19)
июл 28 08:52:56.371130 kernel: Bluetooth: hci0: Reading supported features failed (-19)
июл 28 08:52:56.371159 kernel: Bluetooth: hci0: sending frame failed (-19)
июл 28 08:52:56.371181 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
июл 28 08:52:56.402944 kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
июл 28 08:52:56.410767 kernel: iwlwifi 0000:01:00.0: WRT: Invalid buffer destination
июл 28 08:53:00.205787 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
июл 28 08:53:06.761842 kernel: kauditd_printk_skb: 29 callbacks suppressed
июл 28 08:53:06.905000 kernel: warning: `meshagent' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

uname -a
Linux pve1 6.8.8-4-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.8-4 (2024-07-26T11:15Z) x86_64 GNU/Linux

dpkg -L pve-firmware | grep iwlwifi-ty-a0-gf-a0.pnvm
/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm.xz

[RandyT_Intel]

Hello AntonP8O,

I need some additional information to assist you better. Could you please provide answers to the following questions?

1. When did the issue start?
2. Have you done any driver and system updates?
3. What troubleshooting steps have you done so far?
4. Are you seeing any error messages?

While I'm reviewing the Proxmox forum, can you run the Intel® System Support Utility for the Linux* Operating System and send the logs here? This will help me diagnose your system issue.

Thank you for your cooperation.

Randy T.

Intel Customer Support Technician

[AntonP8O · Accepted solution]

Thx for u reply.
I fix my problem, in my case with proxmox need use networking, not NetworkManager :

Not need NAT for access to my VMs from LAN or WAN.
Read this https://bugzilla.proxmox.com/show_bug.cgi?id=5289
Reinstall this packets for clear configuration:

Code:

apt reinstall wpasupplicant iw wireless-tools

1) Configure you network like this:

Bash:

auto wlp1s0
iface wlp1s0 inet static
        wpa-ssid DevOpsNet
        wpa-psk MyPassFromHackerAss

auto vmbr0
iface vmbr0 inet static
    pre-up iw dev wlp1s0 set 4addr on
        address 192.168.3.44/24
        gateway 192.168.3.1
        bridge-ports wlp1s0
        bridge-stp off
        bridge-fd 0

2) Restart network:

Bash:

systemctl restart networking

3) Restart You VMs for apply new networking.
After this, i have access from my PC to VMs without NAT or VPN

[RandyT_Intel]

Hello AntonP80,

Thank you for the update. I'm glad to hear that you were able to fix the problem. If you need any assistance in the future, you can reach us again.

Randy T

Intel Customer Support Technician