MT7916: broadcast not working after successful EAP auth
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have an issue using the AsiaRF MT7916 module on an aarch64 platform compiled with NXP kernel 6.1.55. I configure an EAP setup with hostapd where the MT7916 is the AP; a client connecting associates to it, then authenticates at a freeradius server which is successful. Now the client requests an IP by DHCP, however the broadcast packets do not flow from the AP to the client! The DHCP Discover is getting replied with an Offer, but this packet is not visible on the client side.
Ping through WLAN works fine, if I configure static IPs on the AP and the client after the radius authentication.
As a reference, I exchanged the MT7916 by another WiFi module (WLE600VX) in the exact same setup, EAP auth worked fine and the client successfully got an IP per DHCP! It looks like this is some driver issue with the MT7916.
Just to mention, the WiFi module works fine with "ordinary" DHCP let's say after WPA2, but not in case of EAP.
I tried it with the firmware from 20230202, the latest firmware from 20240824 shows no difference.
Any ideas ?
Thanks
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 reproducing the MT7916 setup on the aarch64 platform with EAP authentication and DHCP, then compare packet handling with the WLE600VX setup. Trace why the DHCP Offer does not reach the client while static-IP ping works; done means identifying the driver behavior responsible or documenting a confirmed fix path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100