wpa_supplicant事件分析


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
    评论
### 回答1: wpa_supplicant是一个开源的Wi-Fi客户端,用于连接无线网络。它支持多种加密方式和认证协议,包括WPA、WPA2、EAP等。wpa_supplicant的源码分析可以帮助我们深入了解它的工作原理和实现细节,从而更好地使用和定制它。具体分析可以从以下几个方面入手: 1. 网络配置和管理:wpa_supplicant支持多种网络配置方式,包括静态配置和动态获取IP地址等。它还提供了一套API接口,可以用于管理网络连接状态、扫描可用网络、获取网络信息等。 2. 安全认证和加密:wpa_supplicant支持多种安全认证和加密方式,包括WPA、WPA2、EAP等。它还提供了一套API接口,可以用于配置和管理安全认证和加密方式。 3. 事件处理和消息传递:wpa_supplicant使用事件和消息来处理网络连接状态、扫描结果、安全认证和加密等。它提供了一套事件处理机制和消息传递机制,可以用于处理各种事件和消息。 4. 代码结构和模块设计:wpa_supplicant的代码结构和模块设计比较清晰,可以帮助我们更好地理解它的实现细节和工作原理。它包括多个模块,如驱动模块、网络配置模块、安全认证模块等。 总之,wpa_supplicant源码分析可以帮助我们深入了解它的工作原理和实现细节,从而更好地使用和定制它。 ### 回答2: wpa_supplicant是一个为无线网络提供WPA/WPA2加密认证的开源软件,它主要用于Linux和Unix操作系统。wpa_supplicant是基于wpa_action而来,可以支持WPA/WPA2的个人和企业级认证方式,对于无线网络的各种强制策略、速率限制以及数据包报错处理等都有了充分的支持。 在wpa_supplicant源码中,主要分为4个模块:配置文件解析、状态机、消息驱动和驱动层。其中,配置文件解析主要完成对配置文件的读取和解析,读取并解析遵循wpa_supplicant的配置格式,将解析到的配置存放在结构体中,并通过对结构体的操作实现了参数的获取、设置等操作。状态机部分是wpa_supplicant最核心的模块,它实现了所有的状态转移和状态迁移,以及根据不同状态发送不同的管理帧,例如扫描请求、认证请求、关联请求等。消息驱动部分主要完成对消息的处理和转发,它会把收到的消息传给状态机,并根据接口类型进行处理。最后,驱动层部分是和无线网卡驱动相关的部分,主要完成各种无线网络操作的具体实现。 在使用wpa_supplicant时,我们可以通过修改配置文件来配置连接属性并启动wpa_supplicant,或者运行wpa_cli命令直接与wpa_supplicant进行交互。在wpa_supplicant中,当SSID和密码被输入后,它会将身份验证消息发送给AP进行身份验证,并根据AP响应更新状态。如果认证成功,则可以进行DHCP分配地址,完成对无线网络的接入。 总之,wpa_supplicant源码分析对于理解无线网络认证和连接过程非常有帮助,它充分利用了状态机的思想,实现了WPA/WPA2的加密认证,可以说是无线网络连接过程中必不可少的一部分。 ### 回答3: wpa_supplicant是一款常用的无线(Wi-Fi)网络实现工具,它采用C语言编写,提供了跨平台的实现。使用wpa_supplicant可以方便地连接和管理无线网络,支持WPA和WPA2等多种安全认证协议。在实现过程中,wpa_supplicant采用了多线程和事件驱动的方式,提高了性能和扩展性。 在wpa_supplicant源码中,主要包含以下几个模块:网络配置、网络扫描、认证、加密、驱动程序和事件处理。其中,网络配置模块主要负责配置网络连接的参数,例如SSID、密码等;网络扫描模块负责扫描附近的无线网络,并返回扫描结果;认证模块和加密模块负责实现WPA和WPA2等安全认证协议;驱动程序模块负责实现无线网卡的驱动程序,不同网卡驱动程序的实现方式各不相同;事件处理模块负责处理各种事件,例如连接成功、认证失败等,并根据不同的事件做出相应的处理。 值得注意的是,wpa_supplicant源码中实现了很多高级功能,例如WPS、P2P等,这些功能大大增强了wpa_supplicant的实用性和扩展性。 总之,wpa_supplicant源码的分析非常复杂,需要对无线网络、网络协议、驱动程序等方面有深入的理解,才能正确地理解和使用wpa_supplicant。对于开发者而言,如果要对wpa_supplicant做出一些改进和扩展,需要熟练掌握wpa_supplicant源码的实现机制和原理,这样才能确保修改的代码正确、高效和健壮。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值