On-board WiFi EAPOL key exchange not responding

Open
#3,213 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, raspberry-pi

Research direction

No source file or test is named. Start by reproducing the WPA-EAP/MSCHAPV2 connection on the Pi Zero W with the 2019-07-10 image and compare the packet trace with the working RTL8188CUS connection, using the reported firmware and kernel versions. Done means the onboard adapter responds to the EAPOL key exchange, obtains a DHCP address, and can reach the gateway.

Written by the indexing model from the issue text.

Description

Trying to connect to WPA-EAP Enterprise with phase2=MSCHAPV2 network using Raspberry Pi Zero W revision 1.1, image reference 2019-07-10.

When I plug-in an external WiFi USB dongle, "RTL8188CUS 802.11n WLAN Adapter" everything works as expected, it connects to the network and receives IP address from DHCP and internet works.

With exactly the same configuration, the on-board WiFi connects, but does not receive any IP. If I use static IP address, I could not even ping the gateway. Here is a packet trace from bringing the interfaces up (I changed the MAC address using macchanger to match the external adapter to rule out any MAC filtering).:

Screenshot

Nisca_ is the Raspberry Pi, Cambridg_ is the AP. The right one contains the working connection attempt through external dongle. Starting with packet 28, EAPOL key exchange is initiated, exchanging 4 key messages and 2 group key messages. The built-in non-working one on the left side has the same connecting trace, the first key message from AP being packet 28, but the Raspberry Pi never responds to that message. The AP tries a couple of times and then gives up.

I am left with no other options than blaming the wireless driver.

System

  • Which model of Raspberry Pi? PiZeroW 1.1
  • Which OS and version (cat /etc/rpi-issue)? 2019-07-10 ...9a4a56c, stage2
  • Which firmware version (vcgencmd version)? 0e6daa5106dd4164474616408e0dc24f997ffcf3 (clean) (release) (start)
  • Which kernel version (uname -a)? 4.19.66+ #1253 Aug 15
Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.