Android WiFi连接过程 wpa_supplicant 日志分析
文章目录
- [Android WiFi连接过程 wpa_supplicant 日志分析](#Android WiFi连接过程 wpa_supplicant 日志分析)
- 一、前言
- 二、普通网络WiFi连接过程
- 三、EAP网络WiFi连接过程
- 四、WiFi连接失败场景日志分析
- 五、总结
一、前言
在Android系统中,WiFi连接是一个复杂的过程,涉及多个层次的交互。
其中,wpa_supplicant 是底层核心组件,负责处理WiFi的认证、加密和连接管理。
通过分析 wpa_supplicant 的日志,我们可以深入了解WiFi连接的完整流程,以及在各种失败场景下的具体原因。
上层日志主要看WifiService和 WifiConnectivityManager 可以看到连接过程,但是底层日志可以看 wpa_supplicant。
查看底层 wpa_supplicant 日志有啥用? 可以查看哪个流程缺少,比如有些情况根本没调用wifi扫描或者wifi连接。
本文将详细介绍普通网络(WPA-PSK)和EAP网络(EAP-TLS/EAP-PEAP)的WiFi连接完整过程,并分析密码错误、认证错误、WiFi不存在等常见失败场景的日志特征。
二、普通网络WiFi连接过程
普通网络通常指使用WPA/WPA2-PSK加密的WiFi网络,连接过程相对简单,主要包括扫描、关联、认证三个阶段。
1、扫描阶段
扫描是WiFi连接的第一步,设备主动搜索周围的WiFi信号。
07-22 22:19:04.234 6635 6657 D wpa_supplicant: nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0
07-22 22:19:04.234 6635 6657 D wpa_supplicant: wlan0: nl80211: Scan trigger
07-22 22:19:04.234 6635 6657 D wpa_supplicant: wlan0: Event SCAN_STARTED (47) received
07-22 22:19:06.156 6635 6657 D wpa_supplicant: nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
07-22 22:19:06.156 6635 6657 D wpa_supplicant: wlan0: nl80211: New scan results available
07-22 22:19:06.157 6635 6657 D wpa_supplicant: nl80211: Received scan results (76 BSSes)
关键日志说明:
| 日志信息 | 说明 |
|---|---|
NL80211_CMD_TRIGGER_SCAN |
触发扫描命令 |
Event SCAN_STARTED (47) |
扫描开始事件 |
NL80211_CMD_NEW_SCAN_RESULTS |
新扫描结果可用 |
Received scan results (76 BSSes) |
收到76个BSS扫描结果 |
2、关联阶段
扫描完成后,设备选择目标WiFi网络并发起关联请求。
07-22 22:19:04.557 6635 6657 D wpa_supplicant: wlan0: selected BSS 34:f7:16:92:87:71 ssid='syrj_5G'
07-22 22:19:04.557 6635 6657 D wpa_supplicant: wlan0: Request association with 34:f7:16:92:87:71
07-22 22:19:04.557 6635 6657 D wpa_supplicant: wlan0: Trying to associate with SSID 'syrj_5G'
07-22 22:19:04.557 6635 6657 D wpa_supplicant: wlan0: State: DISCONNECTED -> ASSOCIATING
07-22 22:19:04.573 6635 6657 D wpa_supplicant: wlan0: Associated with 34:f7:16:92:87:71
07-22 22:19:04.573 6635 6657 D wpa_supplicant: wlan0: State: ASSOCIATING -> ASSOCIATED
关键日志说明:
| 日志信息 | 说明 |
|---|---|
selected BSS ... ssid='xxx' |
选择目标BSS |
Request association with ... |
请求关联 |
Trying to associate with SSID 'xxx' |
尝试关联 |
State: DISCONNECTED -> ASSOCIATING |
状态转换:断开→关联中 |
Associated with ... |
关联成功 |
State: ASSOCIATING -> ASSOCIATED |
状态转换:关联中→已关联 |
3、认证阶段(4-Way Handshake)
关联成功后,进行4-Way Handshake认证,这是WPA/WPA2-PSK的核心认证过程。
07-22 22:19:04.573 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 1 of 4-Way Handshake
07-22 22:19:04.573 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 2 of 4-Way Handshake
07-22 22:19:04.574 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 3 of 4-Way Handshake
07-22 22:19:04.574 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 4 of 4-Way Handshake
07-22 22:19:04.574 6635 6657 D wpa_supplicant: wlan0: WPA: Key negotiation completed with 34:f7:16:92:87:71 [PTK=CCMP GTK=CCMP]
关键日志说明:
| 日志信息 | 说明 |
|---|---|
WPA: RX message 1 of 4-Way Handshake |
收到第1个握手消息 |
WPA: TX message 2 of 4-Way Handshake |
发送第2个握手消息 |
WPA: RX message 3 of 4-Way Handshake |
收到第3个握手消息 |
WPA: TX message 4 of 4-Way Handshake |
发送第4个握手消息 |
Key negotiation completed ... |
密钥协商完成 |
4、Group Handshake阶段
4-Way Handshake完成后,进行Group Handshake,获取组密钥(GTK)。
07-22 22:19:04.575 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 1 of Group Handshake
07-22 22:19:04.575 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 2 of Group Handshake
07-22 22:19:04.575 6635 6657 D wpa_supplicant: wlan0: State: ASSOCIATED -> COMPLETED
关键日志说明:
| 日志信息 | 说明 |
|---|---|
WPA: RX message 1 of Group Handshake |
收到Group Handshake第1个消息 |
WPA: TX message 2 of Group Handshake |
发送Group Handshake第2个消息 |
State: ASSOCIATED -> COMPLETED |
状态转换:已关联→连接完成 |
5、连接成功
07-22 22:19:04.575 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 34:f7:16:92:87:71 completed [id=0 id_str=]
关键日志说明:
| 日志信息 | 说明 |
|---|---|
CTRL-EVENT-CONNECTED |
连接成功事件 |
Connection to ... completed |
连接完成 |
普通网络连接完整流程图
扫描触发 (SCAN_STARTED)
↓
扫描完成 (NEW_SCAN_RESULTS)
↓
选择BSS (selected BSS)
↓
请求关联 (Request association)
↓
关联中 (ASSOCIATING)
↓
关联成功 (ASSOCIATED)
↓
4-Way Handshake (消息1→2→3→4)
↓
密钥协商完成 (Key negotiation completed)
↓
Group Handshake (消息1→2)
↓
连接完成 (COMPLETED)
↓
CTRL-EVENT-CONNECTED
三、EAP网络WiFi连接过程
EAP网络(如EAP-TLS、EAP-PEAP)是企业级WiFi网络,连接过程比普通网络复杂,增加了EAP认证阶段。
1、扫描阶段(与普通网络相同)
07-21 10:42:53.884 26447 26447 D wpa_supplicant: nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0
07-21 10:42:53.884 26447 26447 D wpa_supplicant: wlan0: nl80211: Scan trigger
07-21 10:42:56.806 26447 26447 D wpa_supplicant: nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
07-21 10:42:56.806 26447 26447 D wpa_supplicant: wlan0: nl80211: New scan results available
2、关联阶段(与普通网络相同)
07-21 10:42:54.575 26447 26447 D wpa_supplicant: wlan0: selected BSS 60:db:15:c2:e6:31 ssid='KTC-SSL-AUTH'
07-21 10:42:54.575 26447 26447 D wpa_supplicant: wlan0: Trying to associate with SSID 'KTC-SSL-AUTH'
07-21 10:42:54.575 26447 26447 D wpa_supplicant: wlan0: State: DISCONNECTED -> ASSOCIATING
07-21 10:42:54.856 26447 26447 D wpa_supplicant: wlan0: Associated with 60:db:15:c2:e6:31
07-21 10:42:54.856 26447 26447 D wpa_supplicant: wlan0: State: ASSOCIATING -> ASSOCIATED
3、EAP认证阶段
这是EAP网络特有的阶段,根据EAP类型不同,认证流程有所差异。
EAP-PEAP认证流程
07-21 10:42:54.940 26447 26447 D wpa_supplicant: EAP: Status notification: accept proposed method (param=PEAP)
07-21 10:42:54.940 26447 26447 D wpa_supplicant: EAP: Initialize selected EAP method: vendor 0 method 25 (PEAP)
07-21 10:42:54.941 26447 26447 D wpa_supplicant: SSL: Initializing TLS engine
07-21 10:42:54.941 26447 26447 D wpa_supplicant: SSL: Set TLS connection parameters
07-21 10:42:54.942 26447 26447 D wpa_supplicant: EAP-PEAP: Start PEAP
07-21 10:42:54.942 26447 26447 D wpa_supplicant: EAP-PEAP: Request Phase 1 Identity
07-21 10:42:54.942 26447 26447 D wpa_supplicant: EAP: TX EAP request (code=1 id=0x01)
07-21 10:42:54.950 26447 26447 D wpa_supplicant: EAP: RX EAP packet (code=2 id=0x01 len=21)
07-21 10:42:54.950 26447 26447 D wpa_supplicant: EAP-PEAP: Phase 1 authentication completed
07-21 10:42:54.950 26447 26447 D wpa_supplicant: EAP-PEAP: Phase 2 authentication started
07-21 10:42:54.950 26447 26447 D wpa_supplicant: EAP: Initialize selected EAP method: vendor 0 method 26 (MSCHAPV2)
07-21 10:42:54.960 26447 26447 D wpa_supplicant: EAP-MSCHAPV2: Generating challenge response
07-21 10:42:54.960 26447 26447 D wpa_supplicant: EAP-MSCHAPV2: Sending challenge response
07-21 10:42:54.970 26447 26447 D wpa_supplicant: EAP-MSCHAPV2: Authentication successful
07-21 10:42:54.970 26447 26447 D wpa_supplicant: EAP-PEAP: Phase 2 authentication completed
07-21 10:42:54.970 26447 26447 D wpa_supplicant: EAP: EAP authentication completed successfully
EAP-PEAP关键日志说明:
| 日志信息 | 说明 |
|---|---|
EAP: Initialize selected EAP method: vendor 0 method 25 (PEAP) |
初始化PEAP方法 |
SSL: Initializing TLS engine |
初始化TLS引擎 |
EAP-PEAP: Start PEAP |
开始PEAP认证 |
EAP-PEAP: Request Phase 1 Identity |
请求Phase 1身份 |
EAP-PEAP: Phase 1 authentication completed |
Phase 1认证完成 |
EAP-PEAP: Phase 2 authentication started |
开始Phase 2认证 |
EAP: Initialize selected EAP method: vendor 0 method 26 (MSCHAPV2) |
初始化MSCHAPV2方法 |
EAP-MSCHAPV2: Generating challenge response |
生成挑战响应 |
EAP-MSCHAPV2: Authentication successful |
MSCHAPV2认证成功 |
EAP-PEAP: Phase 2 authentication completed |
Phase 2认证完成 |
EAP: EAP authentication completed successfully |
EAP认证成功完成 |
EAP-TLS认证流程
07-20 22:48:55.940 26447 26447 D wpa_supplicant: EAP: Status notification: accept proposed method (param=TLS)
07-20 22:48:55.940 26447 26447 D wpa_supplicant: EAP: Initialize selected EAP method: vendor 0 method 13 (TLS)
07-20 22:48:55.940 26447 26447 D wpa_supplicant: SSL: Initializing TLS engine keystore
07-20 22:48:55.940 26447 26447 W wpa_supplicant: EVP_PKEY_from_keystore2:376 Keystore backend used with legacy alias prefix - ignoring.
07-20 22:48:55.941 26447 26447 E wpa_supplicant: EVP_PKEY_from_keystore2:401 Keystore getKeyEntry returned service specific error: 7
07-20 22:48:55.942 26447 26447 E wpa_supplicant: ENGINE: cannot load private key with id 'USRPKEY_le-59'
07-20 22:48:55.942 26447 26447 I wpa_supplicant: TLS: Failed to initialize engine
07-20 22:48:55.942 26447 26447 I wpa_supplicant: EAP-TLS: Failed to initialize SSL.
07-20 22:48:55.942 26447 26447 I wpa_supplicant: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)
EAP-TLS失败关键日志说明:
| 日志信息 | 说明 |
|---|---|
EAP: Initialize selected EAP method: vendor 0 method 13 (TLS) |
初始化TLS方法 |
SSL: Initializing TLS engine keystore |
初始化TLS引擎 |
EVP_PKEY_from_keystore2:376 Keystore backend used with legacy alias prefix - ignoring. |
警告:旧版别名前缀被忽略 |
EVP_PKEY_from_keystore2:401 Keystore getKeyEntry returned service specific error: 7 |
错误:KeyStore获取私钥失败 |
ENGINE: cannot load private key with id 'USRPKEY_le-59' |
错误:无法加载私钥 |
TLS: Failed to initialize engine |
TLS引擎初始化失败 |
EAP-TLS: Failed to initialize SSL. |
EAP-TLS SSL初始化失败 |
EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS) |
EAP-TLS方法初始化失败 |
4、4-Way Handshake阶段(与普通网络相同)
07-21 10:42:54.975 26447 26447 D wpa_supplicant: wlan0: WPA: RX message 1 of 4-Way Handshake
07-21 10:42:54.975 26447 26447 D wpa_supplicant: wlan0: WPA: TX message 2 of 4-Way Handshake
07-21 10:42:54.976 26447 26447 D wpa_supplicant: wlan0: WPA: RX message 3 of 4-Way Handshake
07-21 10:42:54.976 26447 26447 D wpa_supplicant: wlan0: WPA: TX message 4 of 4-Way Handshake
07-21 10:42:54.976 26447 26447 D wpa_supplicant: wlan0: WPA: Key negotiation completed with 60:db:15:c2:e6:31 [PTK=CCMP GTK=CCMP]
5、Group Handshake阶段(与普通网络相同)
07-21 10:42:54.977 26447 26447 D wpa_supplicant: wlan0: WPA: RX message 1 of Group Handshake
07-21 10:42:54.977 26447 26447 D wpa_supplicant: wlan0: WPA: TX message 2 of Group Handshake
07-21 10:42:54.977 26447 26447 D wpa_supplicant: wlan0: State: ASSOCIATED -> COMPLETED
6、连接成功
07-21 10:42:54.977 26447 26447 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 60:db:15:c2:e6:31 completed [id=0 id_str=]
EAP网络连接完整流程图
扫描触发 (SCAN_STARTED)
↓
扫描完成 (NEW_SCAN_RESULTS)
↓
选择BSS (selected BSS)
↓
请求关联 (Request association)
↓
关联中 (ASSOCIATING)
↓
关联成功 (ASSOCIATED)
↓
EAP认证阶段
↓
┌─────────────────────────┐
│ EAP-PEAP: │
│ Phase 1 (TLS握手) │
│ Phase 2 (MSCHAPV2) │
└─────────────────────────┘
↓
EAP认证成功 (EAP authentication completed)
↓
4-Way Handshake (消息1→2→3→4)
↓
密钥协商完成 (Key negotiation completed)
↓
Group Handshake (消息1→2)
↓
连接完成 (COMPLETED)
↓
CTRL-EVENT-CONNECTED
四、WiFi连接失败场景日志分析
1、密码错误场景
当WiFi密码错误时,4-Way Handshake阶段会失败。
07-22 22:19:19.573 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 1 of 4-Way Handshake
07-22 22:19:19.573 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 2 of 4-Way Handshake
07-22 22:19:19.574 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 3 of 4-Way Handshake
07-22 22:19:19.574 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 4 of 4-Way Handshake
07-22 22:19:19.575 6635 6657 D wpa_supplicant: wlan0: WPA: Key negotiation completed with 34:f7:16:92:87:71 [PTK=CCMP GTK=CCMP]
07-22 22:19:19.575 6635 6657 D wpa_supplicant: wlan0: WPA: RX message 1 of Group Handshake
07-22 22:19:19.575 6635 6657 D wpa_supplicant: wlan0: WPA: TX message 2 of Group Handshake
07-22 22:19:19.575 6635 6657 D wpa_supplicant: wlan0: State: ASSOCIATED -> COMPLETED
07-22 22:19:19.575 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 34:f7:16:92:87:71 completed [id=0 id_str=]
07-22 22:19:19.600 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=34:f7:16:92:87:71 reason=15
07-22 22:19:19.600 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="syrj_5G" auth_failures=1 duration=30 reason=WRONG_KEY
密码错误关键日志说明:
| 日志信息 | 说明 |
|---|---|
reason=15 |
断开原因码15(认证超时) |
reason=WRONG_KEY |
错误原因:密钥错误 |
auth_failures=1 |
认证失败次数 |
duration=30 |
临时禁用时长30秒 |
密码错误流程:
4-Way Handshake完成
↓
Group Handshake完成
↓
连接成功 (CTRL-EVENT-CONNECTED)
↓
认证超时 (reason=15)
↓
断开连接 (CTRL-EVENT-DISCONNECTED)
↓
临时禁用网络 (CTRL-EVENT-SSID-TEMP-DISABLED)
2、认证错误场景(EAP网络)
当EAP认证失败时,会在EAP认证阶段失败。
07-20 22:48:55.940 26447 26447 D wpa_supplicant: EAP: Status notification: accept proposed method (param=TLS)
07-20 22:48:55.940 26447 26447 D wpa_supplicant: EAP: Initialize selected EAP method: vendor 0 method 13 (TLS)
07-20 22:48:55.940 26447 26447 D wpa_supplicant: SSL: Initializing TLS engine keystore
07-20 22:48:55.941 26447 26447 E wpa_supplicant: EVP_PKEY_from_keystore2:401 Keystore getKeyEntry returned service specific error: 7
07-20 22:48:55.942 26447 26447 E wpa_supplicant: ENGINE: cannot load private key with id 'USRPKEY_le-59'
07-20 22:48:55.942 26447 26447 I wpa_supplicant: TLS: Failed to initialize engine
07-20 22:48:55.942 26447 26447 I wpa_supplicant: EAP-TLS: Failed to initialize SSL.
07-20 22:48:55.942 26447 26447 I wpa_supplicant: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)
07-20 22:49:03.648 26447 26447 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=60:db:15:c2:e6:31 reason=3
07-20 22:49:03.648 26447 26447 I wpa_supplicant: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="KTC-SSL-AUTH" auth_failures=1 duration=30 reason=AUTH_FAILED
认证错误关键日志说明:
| 日志信息 | 说明 |
|---|---|
EVP_PKEY_from_keystore2:401 Keystore getKeyEntry returned service specific error: 7 |
KeyStore获取私钥失败 |
ENGINE: cannot load private key with id 'USRPKEY_le-59' |
无法加载私钥 |
TLS: Failed to initialize engine |
TLS引擎初始化失败 |
EAP-TLS: Failed to initialize SSL. |
EAP-TLS SSL初始化失败 |
EAP: Failed to initialize EAP method |
EAP方法初始化失败 |
reason=3 |
断开原因码3(认证失败) |
reason=AUTH_FAILED |
错误原因:认证失败 |
EAP有几种类型,这里只举例了TLS类型的网络失败的情况。
3、WiFi不存在场景
当WiFi网络不存在时,扫描阶段就会失败。
07-22 22:19:23.234 6635 6657 D wpa_supplicant: nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0
07-22 22:19:23.234 6635 6657 D wpa_supplicant: wlan0: nl80211: Scan trigger
07-22 22:19:23.234 6635 6657 D wpa_supplicant: wlan0: Event SCAN_STARTED (47) received
07-22 22:19:25.156 6635 6657 D wpa_supplicant: nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0
07-22 22:19:25.156 6635 6657 D wpa_supplicant: wlan0: nl80211: New scan results available
07-22 22:19:25.157 6635 6657 D wpa_supplicant: nl80211: Received scan results (76 BSSes)
07-22 22:19:25.158 6635 6657 D wpa_supplicant: wlan0: No BSSID found for SSID 'NonExistentWiFi'
07-22 22:19:25.158 6635 6657 D wpa_supplicant: wlan0: Skip connection to disabled network
07-22 22:19:25.158 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
07-22 22:19:25.158 6635 6657 I wpa_supplicant: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="NonExistentWiFi" auth_failures=1 duration=30 reason=NETWORK_NOT_FOUND
WiFi不存在关键日志说明:
| 日志信息 | 说明 |
|---|---|
No BSSID found for SSID 'xxx' |
找不到指定SSID的BSS |
Skip connection to disabled network |
跳过连接到禁用的网络 |
reason=3 |
断开原因码3 |
reason=NETWORK_NOT_FOUND |
错误原因:网络未找到 |
4、连接失败场景对比表
| 失败场景 | 失败阶段 | 关键日志 | 原因码 |
|---|---|---|---|
| 密码错误 | 4-Way Handshake后 | reason=WRONG_KEY |
15 |
| 认证错误(EAP) | EAP认证阶段 | EAP: Failed to initialize EAP method |
3 |
| WiFi不存在 | 扫描阶段 | No BSSID found for SSID |
3 |
| 关联失败 | 关联阶段 | Association request rejected |
2/4 |
| DHCP失败 | IP获取阶段 | CTRL-EVENT-DHCP-FAILURE |
1 |
五、总结
1、普通网络 vs EAP网络连接过程对比
| 阶段 | 普通网络(WPA-PSK) | EAP网络(EAP-TLS/PEAP) |
|---|---|---|
| 扫描 | ✅ 相同 | ✅ 相同 |
| 关联 | ✅ 相同 | ✅ 相同 |
| EAP认证 | ❌ 无 | ✅ 有(Phase 1+Phase 2) |
| 4-Way Handshake | ✅ 相同 | ✅ 相同 |
| Group Handshake | ✅ 相同 | ✅ 相同 |
| 连接成功 | ✅ 相同 | ✅ 相同 |
核心区别:EAP网络在关联成功后增加了EAP认证阶段,这是企业级WiFi安全的关键。
2、wpa_supplicant状态转换总结
DISCONNECTED
↓ (扫描发现网络)
SCANNING
↓ (选择目标网络)
DISCONNECTED
↓ (请求关联)
ASSOCIATING
↓ (关联成功)
ASSOCIATED
↓ (EAP认证完成/4-Way Handshake完成)
4WAY_HANDSHAKE
↓ (密钥协商完成)
GROUP_HANDSHAKE
↓ (Group Handshake完成)
COMPLETED
↓ (连接成功)
CONNECTED
3、底层wifi关键日志关键字总结
| 阶段 | 关键字 |
|---|---|
| 扫描 | SCAN_STARTED、NEW_SCAN_RESULTS、Received scan results |
| 关联 | selected BSS、Trying to associate、Associated with |
| EAP认证 | EAP: Initialize selected EAP method、EAP authentication completed |
| 4-Way Handshake | WPA: RX message X of 4-Way Handshake、Key negotiation completed |
| Group Handshake | WPA: RX message X of Group Handshake |
| 连接成功 | CTRL-EVENT-CONNECTED、Connection to ... completed |
| 连接失败 | CTRL-EVENT-DISCONNECTED、reason=、CTRL-EVENT-SSID-TEMP-DISABLED |
通过分析这些关键日志,可以快速定位WiFi连接过程中的问题所在,无论是密码错误、认证失败还是网络不存在,都可以通过日志中的特定关键字进行判断。
4、 上层主要日志和流程
Wifi相关日志的关键字都是:wifi,会有点多
wifi开关的日志是:WifiService
底层相关日志:wpa_supplicant、wifi-service
其他相关:WifiNative、WifiHAL
日志过滤:
logcat | grep -i wifi
logcat | grep -iE "WifiService|WifiNative"
logcat | grep -iE "WifiService|wpa_supplicant|wifi-service|WifiNative|WifiHAL|DHCP|wlan"
------------------------------------------------
流程:
//wifi开启
// 1. 用户触发开启 WiFi(如点击开关)
WifiService、WifiController
//wifi扫描
WifiService、WifiScanRequestProxy、WifiHAL
// 2. 扫描完成,获取结果
WifiScanner、WifiScanResults
//wifi选择+准备连接
ThroughputScorer、WifiConnectivityManager、WifiConfigManager
// 2. 准备连接(加载配置,如密码)
WifiConnectivityManager、WifiConfigManager:、WifiStateMachine
// 1. 开始连接,状态从 Disconnected 切换到 Connecting
WifiStateMachine、WifiNative
// 2. 认证阶段(验证密码)、4次握手
SupplicantStateTracker、wpa_supplicant、SupplicantStateTracker、WifiStateMachine
// 启动 DHCP 客户端、分配ip
DhcpClient
//网络状态变为可用
WifiStateMachine、ConnectivityService
// 通知连接成功
WifiService、ConnectivityManager
相关文章:
Android16 Wifi打开到自动连接的主要日志过程分析介绍:
https://blog.csdn.net/wenzhi20102321/article/details/153836310
Android wifi开发调试总结:
https://blog.csdn.net/wenzhi20102321/article/details/147595608