Belkin RT3200/MT7915E: WED + Intel AX200 = iwlwifi 0000:03:00.0: Unhandled alg: 0x703
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
When enabling WED on my Belkin RT3200, the Intel AX200 occasionally shows the following message:
iwlwifi 0000:03:00.0: Unhandled alg: 0x703
I've monitored the same machine for a week with WED disabled and this issue does not appear. I suspect that occasional garbage packages reach the client. On older kernels I've seen this issue lead to firmware hangs/resets on the client side, but the log I'm currently looking at does not mention any such firmware resets. It may have gotten more robust with updates on either router- or client side.
Router:
- Belkin RT3200
- OpenWrt SNAPSHOT r21968-acd8e94d20 / LuCI Master git-23.013.73089-9634086 ("mt76: update PKG_SOURCE_HASH")
- Kernel 5.15.90
- WPA3 SAE
- 2.4GHz: .n, 40MHz
- 5GHz: .ax, 80MHz
Client:
- Fedora 37, kernel 6.1.8-200.fc37.x86_64
- Intel AX200, firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm
Note that this client-server combination also experiences #724 , regardless of whether WED is enabled or disabled.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #724 and reproducing the Belkin RT3200 setup with WED enabled and disabled. Compare the Intel AX200 logs across both configurations, including the reported firmware and kernel versions. Done means determining whether WED causes the unhandled algorithm message and documenting or addressing the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100