wpa_supplicant事件分析

最新推荐文章于 2023-07-27 11:21:07 发布
最新推荐文章于 2023-07-27 11:21:07 发布
阅读量5.4k 收藏 1
点赞数
分类专栏： 源码解析
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/hpp205/article/details/51458671
版权


WPA Client Persistent Connect Event


[Thu May 19 11:50:52.031 2016] <3>P2P-INVITATION-RECEIVED sa=f6:5c:89:91:82:1b persistent=1
[Thu May 19 11:50:53.062 2016] <3>CTRL-EVENT-SCAN-STARTED 
[Thu May 19 11:50:53.203 2016] <3>CTRL-EVENT-SCAN-RESULTS 
[Thu May 19 11:50:53.218 2016] <3>WPS-AP-AVAILABLE 
[Thu May 19 11:50:53.218 2016] <3>Trying to associate with f6:5c:89:91:8a:1b (SSID='DIRECT-EDDESKTOP-R4UMDB5FLQL' freq=2412 MHz)
[Thu May 19 11:50:53.281 2016] <3>Associated with f6:5c:89:91:8a:1b
[Thu May 19 11:50:53.312 2016] <3>CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success)
[Thu May 19 11:50:53.328 2016] <3>WPA: Key negotiation completed with f6:5c:89:91:8a:1b [PTK=CCMP GTK=CCMP]
[Thu May 19 11:50:53.359 2016] <3>CTRL-EVENT-CONNECTED - Connection to f6:5c:89:91:8a:1b completed [id=2 id_str=]
[Thu May 19 11:50:53.390 2016] <3>P2P-GROUP-STARTED p2p0 client ssid="DIRECT-EDDESKTOP-R4UMDB5FLQL" freq=2412 psk=e420d09d92128e835e5f30e86ef37d15bd6cb2f2a0a1f3a165072a7ef69672c2 go_dev_addr=f6:5c:89:91:82:1b [PERSISTENT]
[Thu May 19 11:51:20.718 2016] <3>CTRL-EVENT-DISCONNECTED bssid=f6:5c:89:91:8a:1b reason=3 locally_generated=1
[Thu May 19 11:51:20.812 2016] <3>P2P-GROUP-REMOVED p2p0 client reason=REQUESTED
[Thu May 19 11:51:20.984 2016] <3>P2P-DEVICE-LOST p2p_dev_addr=f6:5c:89:91:82:1b
[Thu May 19 11:51:21.078 2016] <3>CTRL-EVENT-SCAN-STARTED 
[Thu May 19 11:51:21.093 2016] <3>CTRL-EVENT-SCAN-RESULTS 
[Thu May 19 11:51:45.875 2016] <3>P2P-DEVICE-FOUND f6:5c:89:91:82:1b p2p_dev_addr=f6:5c:89:91:82:1b pri_dev_type=1-0050F200-0 name='DESKTOP-R4UMDB5' config_methods=0x11e8 dev_capab=0x24 group_capab=0x28 wfd_dev_info=0x01101c440006 new=1


p2papp normal pair pin event

P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 22 0 0c000b00085f7773626465762a00
P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1
P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 conncap=1 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=7 mac=60:57:18:cd:b5:9b dev_passwd_id=1
P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82
P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=0
P2P-GO-NEG-REQUEST 60:57:18:cd:b5:9b dev_passwd_id=1
P2P-GO-NEG-SUCCESS role=client freq=2462 ht40=0 peer_dev=60:57:18:cd:b5:9b peer_iface=62:57:18:cd:b5:9a wps_method=Display
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-OoDESKTOP-M7ALB23DODB' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-STATUS status='started' parameter=''
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1
CTRL-EVENT-EAP-STATUS status='accept proposed method' parameter='WSC'
CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected
WPS-CRED-RECEIVED 
WPS-SUCCESS 
P2P-GROUP-FORMATION-SUCCESS 
CTRL-EVENT-EAP-STATUS status='completion' parameter='failure'
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-DISCONNECTED bssid=62:57:18:cd:b5:9a reason=3 locally_generated=1
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-OoDESKTOP-M7ALB23DODB' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
WPA: Key negotiation completed with 62:57:18:cd:b5:9a [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 62:57:18:cd:b5:9a completed [id=0 id_str=]
P2P-GROUP-STARTED p2p0 client ssid="DIRECT-OoDESKTOP-M7ALB23DODB" freq=2462 psk=53231c654fd98bfd544b110454f6a9e3baf256d1d27c68dbf320f6d406c9f4b8 go_dev_addr=60:57:18:cd:b5:9b [PERSISTENT] ip_addr=192.168.137.247 ip_mask=255.255.255.0 go_ip_addr=192.168.137.1


p2papp normal persistent event

P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 25 0 0c000b00085f7773626465762a00
P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1
P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=8 mac=60:57:18:cd:b5:9b persist=1 role=client
P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE 
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-OoDESKTOP-M7ALB23DODB' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success)
WPA: Key negotiation completed with 62:57:18:cd:b5:9a [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 62:57:18:cd:b5:9a completed [id=2 id_str=]
P2P-GROUP-STARTED p2p0 client ssid="DIRECT-OoDESKTOP-M7ALB23DODB" freq=2462 psk=53231c654fd98bfd544b110454f6a9e3baf256d1d27c68dbf320f6d406c9f4b8 go_dev_addr=60:57:18:cd:b5:9b [PERSISTENT] ip_addr=192.168.137.247 ip_mask=255.255.255.0 go_ip_addr=192.168.137.1


p2papp agStart pair pin event

P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 5 0 0c000b00085f7773626465762a00
P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 5 0 0c000b00085f7773626465762a00
P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1
P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 conncap=2 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=3 mac=60:57:18:cd:b5:9b dev_passwd_id=1 join=62:57:18:cd:b5:9a
P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-STARTED 
P2P-DEVICE-FOUND 62:57:18:cd:b5:9a p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='' config_methods=0x11e8 dev_capab=0x25 group_capab=0x8b wfd_dev_info=0x01101c440006 vendor_elems=1 new=0
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE-PIN 
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-JRDESKTOP-M7ALB23msRU' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-STATUS status='started' parameter=''
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1
CTRL-EVENT-EAP-STATUS status='accept proposed method' parameter='WSC'
CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected
WPS-CRED-RECEIVED 
WPS-SUCCESS 
P2P-GROUP-FORMATION-SUCCESS 
CTRL-EVENT-EAP-STATUS status='completion' parameter='failure'
CTRL-EVENT-EAP-FAILURE EAP authentication failed
CTRL-EVENT-DISCONNECTED bssid=62:57:18:cd:b5:9a reason=3 locally_generated=1
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-JRDESKTOP-M7ALB23msRU' freq=2462 MHz)
CTRL-EVENT-ASSOC-REJECT status_code=1
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE 
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-JRDESKTOP-M7ALB23msRU' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
WPA: Key negotiation completed with 62:57:18:cd:b5:9a [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 62:57:18:cd:b5:9a completed [id=0 id_str=]
P2P-GROUP-STARTED p2p0 client ssid="DIRECT-JRDESKTOP-M7ALB23msRU" freq=2462 psk=8ac46586d8bdab40947e329959f93f92504e9f7c1e92493f6afe7a587d09414d go_dev_addr=60:57:18:cd:b5:9b [PERSISTENT] ip_addr=192.168.137.247 ip_mask=255.255.255.0 go_ip_addr=192.168.137.1


p2papp agStart persistent event

P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 new=1
P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=9 mac=60:57:18:cd:b5:9b persist=0 role=client
P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82
CTRL-EVENT-SCAN-STARTED 
CTRL-EVENT-SCAN-RESULTS 
WPS-AP-AVAILABLE 
Trying to associate with 62:57:18:cd:b5:9a (SSID='DIRECT-JRDESKTOP-M7ALB23msRU' freq=2462 MHz)
Associated with 62:57:18:cd:b5:9a
WPA: Key negotiation completed with 62:57:18:cd:b5:9a [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 62:57:18:cd:b5:9a completed [id=1 id_str=]
P2P-GROUP-STARTED p2p0 client ssid="DIRECT-JRDESKTOP-M7ALB23msRU" freq=2462 psk=8ac46586d8bdab40947e329959f93f92504e9f7c1e92493f6afe7a587d09414d go_dev_addr=60:57:18:cd:b5:9b [PERSISTENT] ip_addr=192.168.137.247 ip_mask=255.255.255.0 go_ip_addr=192.168.137.1


p2ps pair pin gc event

1. P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 26 0 0c000b00085f7773626465762a00

2. P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1

3. P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 conncap=2 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=1d mac=60:57:18:cd:b5:9b dev_passwd_id=1 join=62:57:18:cd:b5:9a

4. P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82


p2ps persistent events

1. P2P-SERV-DISC-REQ 2462 60:57:18:cd:b5:9b 12 0 0c000b00085f7773626465762a00

2. P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1

3. P2PS-PROV-DONE 60:57:18:cd:b5:9b status=0 adv_id=1 adv_mac=12:9f:a9:e9:e9:2b session=5 mac=60:57:18:cd:b5:9b persist=1 role=GO

4. P2P-PROV-DISC-SHOW-PIN 60:57:18:cd:b5:9b 12345670 p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82


p2p pair pbc event

1. P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=1

2. P2P-PROV-DISC-PBC-REQ 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82

3. P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x25 group_capab=0x82 wfd_dev_info=0x01101c440006 new=0

4. P2P-GO-NEG-REQUEST 60:57:18:cd:b5:9b dev_passwd_id=4

5. P2P-GO-NEG-SUCCESS role=client freq=2462 ht40=0 peer_dev=60:57:18:cd:b5:9b peer_iface=62:57:18:cd:b5:9a wps_method=PBC


p2p persistent pbc event

P2P-DEVICE-FOUND 60:57:18:cd:b5:9b p2p_dev_addr=60:57:18:cd:b5:9b pri_dev_type=1-0050F200-0 name='DESKTOP-M7ALB23' config_methods=0x11e8 dev_capab=0x0 group_capab=0x0 wfd_dev_info=0x01101c440006 new=1

P2P-INVITATION-RECEIVED sa=60:57:18:cd:b5:9b persistent=1



小小黄
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
wpa_supplicant 状态机的切换以及事件驱动
chenmi123321的博客
11-01 1375
wpa_supplicant 状态机的切换以及事件驱动
wpa_supplicant _ hostapd：Wi-Fi Direct-P2P模块.pdf
05-26
supplicant里面的P2P函数接口说明，附带示例程序。研究80211协议的朋友可以参考学习。WIFI DIRECT技术相关资料
Android4.4 Wi-Fi P2P WifiP2pService中消息处理
hanhan1016的专栏
08-17 2893
1.DISCOVER_PEERS 在函数discoverPeers中，发送一条DISCOVER_PEERS消息，来开始P2P设备搜索。 /** * Initiate peer discovery. A discovery process involves scanning for available Wi-Fi peers * for the purpose of
wpa_supplicant2.6之P2P测试操作操作PC端与android设备的互相操作
分享嵌入式,移动端,智能应用,数据库等专业板块,记录知识碎片！！！
09-11 4993
OK CTRL-EVENT-SCAN-STARTED CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN CTRL-EVENT-SCAN-STARTED P2P-DEVICE-FOUND 6a:df:dd:a5:07:9b p2p_dev_addr=6a:df:dd:a5:07:9b pri_dev_type=10-0050F2
wpa_supplicant wps手册的翻译
良师，益友
02-25 8730
看了《Wi-Fi Protected Setup in the wpa_supplicant》这篇文档，我想你就懂wps是怎么一回事了。    一、前言     The goal of Wi-Fi Protected Setup (WPS) is to automate the creation of a secure wireless network. The protocol re
wpa_supplicant_8 源码
10-28
《深入剖析wpa_supplicant_8源码：无线网络安全连接的核心》 在无线网络的世界里，wpa_supplicant是一个至关重要的组件，它负责处理无线网络的连接与安全认证。本资源提供的是wpa_supplicant_8的源码，对于那些想要...
wpa_supplicant-2.0_wpa_supplicant_
10-01
《wpa_supplicant 2.0：无线网络安全的守护者》 wpa_supplicant是一款开源的无线网络连接管理工具，其2.0版本是它在无线网络安全领域的一个重要里程碑。这款软件的主要职责是处理Wi-Fi连接，特别是对于WPA（Wi-Fi ...
wpa_supplicant-0.6.9 源码
10-09
5. **事件处理**：`wpa_supplicant` 监听网络事件，如连接成功、信号强度变化等，并通过控制接口向用户或系统报告。 **三、学习与分析** 1. **代码阅读**：通过阅读源码，可以深入理解 Wi-Fi 连接过程中的各个步骤...
wpa_supplicant软件架构分析.pdf
10-14
wpa_supplicant软件架构分析.pdf
node_wpa_supplicant:Node.js库，用于更新和重新启动在Linux wpa_supplicant下运行的无线适配器
05-05
4. **JavaScript API设计**：分析node_wpa_supplicant库提供的API，理解如何通过JavaScript调用这些API来控制无线网络适配器。 5. **异步编程**：因为网络操作通常是异步的，所以需要掌握Promise、async/await等异步...
dev_info、dev_dbg、dev_err及动态调试
eurphan_y的博客
05-23 1726
目前在kernel驱动代码中，都不再建议直接使用printk直接添加打印信息，而是使用dev_info，dev_dbg，dev_err之类的函数代替，虽然这些dev_xxx函数的本质还是使用printk打印的，但是相比起printk： 支持打印模块信息、dev信息 支持动态调试(dynamic debug)方式 下面简述下这几个dev_xxx函数的基本使用规则，以及动态调试使用方式。 dev_info()： 启动过程、或者模块加载过程等“通知类的”信息等，一般只会通知一次，例如probe函数； de.
Android wpa_cli 调试方法(adb shell 命令)
bo_的博客
05-08 3930
svn wifi able / svn wif disable 关闭和打开wifi adb shell 和adb区别！ 常用的adb shell命令 ：如果输入命令无效'b，确认是不是在root目录下！su切换 1. 打开wlan0 这个没什么好说的，ifconfig wlan0 up 2、启动wpa_supplicant 命令如下：可以参考下自己init.xxx.rc是如...
WiFi Direct即P2P协议学习笔记
热门推荐
Lizune
04-24 1万+
文章目录前言一、P2P的模型1.1 P2P的组成1.2 P2P的拓扑1.3 P2P并发模式1.4 功能和服务1.4.1 基本功能和服务1.4.2 P2P的特殊功能和服务1.4.3 P2P的两种地址二、P2P discovery阶段2.1 介绍2.2 P2P设备Discovery过程2.3 前言 在WiFi直连（WiFi Direct，也称为peer-to-peer，P2P）中，设备可以不通过AP（Access Point）进行连接。在P2P group中，称为GO（Group Owner）的设备具有像A
WIFI P2P In Linux
maimang1001的专栏
09-28 1329
WIFI P2P In Linux – SimpleBlogsMost of the Andriod users know about file sharing tools which lets the users to share the data directly with other user like, share it the most popular one. This is very much useful when there is no A.P to relay the traffic f
linux扫描wifi信号脚本,适用于Linux的人类可解析的WiFi扫描工具在哪...
weixin_36470210的博客
05-02 507
大多数Linux平台都附带了wpa_supplicant,它可以单独使用,也可以由NetworkManager等其他“框架”及其CLI工具wpa_cli使用.我不知道更新的系统方法(它往往会取代其他所有方法……).# wpa_cliwpa_cli v2.6[...]Selected interface 'wlan0'Interactive mode> scanOK<3>CTRL-...
linux+wifi+p2p+实例,c - 通过wpa_supplicant启用到Linux的WiFi P2P链接 - 堆栈内存溢出
weixin_35544325的博客
05-13 1706
我通过wpa_supplicant和一个简单的C程序[1]调用wpa_ctrl API [2]启用到Linux主机的WiFi P2P连接。 在通过Nexus 7 Android平板电脑连接然后断开连接后，Linux主机将从平板电脑的P2P对等列表中消失，并且仅在重新启动主机后重新出现。 我尝试重新发布p2p_ext_listen，重新启动wpa_supplicant，并使用modprobe取消...
【MTK平台】【wpa_supplicant】关于wpa_supplicant_8/src/p2p/p2p_go_neg.c文件的介绍
最新发布
weixin_47456647的博客
07-27 801
1. p2p_connect_send接受来自 p2p.c 文件中调用p2p_connect方法发送的GON Request帧。本文主要介绍external/wpa_supplicant_8/src/p2p/p2p_go_neg.c文件。2. p2p_process_go_neg_resp处理来自GON Response帧的处理流程。再看下p2p_process_go_neg_resp方法。先看下p2p_connect_send方法。这里主要介绍2个方法。
wpa_supplicant源码分析
06-28
wpa_supplicant的源码分析可以帮助我们深入了解它的工作原理和实现细节，从而更好地使用和定制它。具体分析可以从以下几个方面入手： 1. 网络配置和管理：wpa_supplicant支持多种网络配置方式，包括静态配置和动态...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值