完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
在43362平台上使用联合测试应用：
平台DPM3A ISM43362M3GYL44初始化 初始化NETXX-DUO V5.7YSP2 创建包池 WLAN MAC地址：C4:7F:51:01:6A:E9 WLAN固件：WL0: 10月23日2017 09:31:05版本5.90.230.22FWID01303030 控制台应用程序 连接试验EPAGTLS WPA2 尝试使用企业EAP-TLS进行连接。为TLSV1.0和TLV1.1工作。TLSv1.2似乎完成了握手，然后接收下面的事件WLCKE.DEAuthIdIn并再次启动连接： WiDeDeEngInEngEngsTysAdHuffer-:EnvivType＝0x2e状态＝0x105原因= 0x20e WICDEDIONJIONSTORY＝0x16 等待密钥交换 WWDIWiFixCuffer-CythOnLoad状态：WICEDID-CouthOyStase= 0x16 WIDEDIONGIONGIONESTESSION处理程序：EnvivType＝0x6状态＝0x0原因： WWDIWiFixCuffer-CythOnLoad状态：WICEDID-CouthOyStase= 0x14 WETEDIONGIONGIONESTESSION处理程序：EnvivType＝0x3状态＝0x0原因： WWDIWiFixCuffer-CythOnLoad状态：WICEDID-CouthOyStase= 0x16 WIDEDIONGIONGIONESTESSION处理程序：EnvivType＝0x10状态＝0x0原因： 为什么在握手完成后接收到错误事件？ 我为TLSV1.1和TLV1.2都包含了日志。 当做， 莱夫 CuxOnthLogLogyEAPTLSV1N1连接器 1.2 K CuxOnthLogLogyEAPTLV1L22FAIL.TXT.ZIP 1.4 K 以上来自于百度翻译 以下为原文 Using join_ent test application on the 43362 platform: Platform DPM3_ISM43362_M3G_L44 initialised Initialising NetX_Duo v5.7_sp2 Creating Packet pools WLAN MAC Address : C4:7F:51:01:6A:E9 WLAN Firmware : wl0: Oct 23 2017 09:31:05 version 5.90.230.22 FWID 01-303030 Console app > join_ent it-test eap_tls wpa2 trying to connect using Enterprise EAP-TLS. Works for TLSv1.0 and TLSv1.1. TLSv1.2 appears to complete the handshake, then receives the following event WLC_E_DEAUTH_IND and starts the connection again: wiced_join_events_handler: event_type=0x2e status=0x105 reason=0x20e wiced_join_status=0x16 wiced_join_events_handler: Waiting Key Exchange wwd_wifi_check_join_status: wiced_join_status=0x16 wiced_join_events_handler: event_type=0x6 status=0x0 reason=0xf wiced_join_status=0x16 wwd_wifi_check_join_status: wiced_join_status=0x14 wiced_join_events_handler: event_type=0x3 status=0x0 reason=0x0 wiced_join_status=0x14 wwd_wifi_check_join_status: wiced_join_status=0x16 wiced_join_events_handler: event_type=0x10 status=0x0 reason=0x0 wiced_join_status=0x16 Any reason why it is receiving error event after completing the handshake? I have included logs for both TLSv1.1 and TLSv1.2 Regards, Leif 
0
|
|
相关推荐
5个回答
|
|
|
添加GRSR
其结果类似于我用THEXX的PEAP测试，TLS1.0／1.1工作，但TLS1.2失败。 以上来自于百度翻译 以下为原文 Add grsr The result is similar to my PEAP test with ThreadX, TLS1.0/1.1 works but TLS1.2 fails. |
|
|
|
|
|
查看EAPHTLVS1.2的日志，似乎TLS握手失败了。我能看见！MbTrsSysSLSH握手在日志中返回-0x138b，但在另一个地方，我看到了错误代码-0xFFFFBCF0。TLVS1.2日志中的WICDEDIONJIONSTORY＝0x16表示CuangOSurSythyIOfFulk标志为0。如果握手完成，如果EAP握手有任何问题，如果有任何连接，请与WiReSARK检查。让我们知道RADIUS服务器以供参考。这个问题是用另一个Wi-Fi芯片复制的吗？
以上来自于百度翻译 以下为原文 Looking at the logs of EAP_TLSv1.2, it appears that the TLS handshake is failing. I could see ! mbedtls_ssl_handshake returned -0x138b in the logs but at another place, I saw error code -0xffffbcf0. The wiced_join_status=0x16 in TLSv1.2 logs indicates that JOIN_SECURITY_COMPLETE flag is 0. Please check with wireshark if the handshake is completing and if there are any problems with EAP handshake and attach the wireshark logs if there are any. Let us know the RADIUS server for reference. Is this issue replicated with another Wi-Fi chip? |
|
|
|
|
asd013 发表于 2018-11-29 13:06 是的，在那个日志中，TLS握手失败了，但是在第一次尝试完成之后（第61行） 然后，第63行显示了错误： WiDeDeEngInEngEngsTysAdHuffer-:EnvivType＝0x2e状态＝0x105原因= 0x20e WICDEDIONJIONSTORY＝0x16 事件= WLCKEYPSKYSUP状态＝WLCXSUPKIKXXCHORATIONS = WLCKEY EXI DEAUTH 在接收PMK时出现错误？ 而TLS1.1返回： WiDeDeEngInEngEngsTysAdHuffer-:EnvivType＝0x2e状态＝0x106原因＝0x200 WICDED CouthOyStase= 0x16 事件＝WLCKEYPSKSUP状态＝WLCX 完成和获取IP地址。 我包括2个新捕获没有失败后重试。 运行Windows网络策略服务器。 我还得弄清楚如何在Windows机器上捕获EAP握手？ 在服务器上运行WiReHARK捕获吗？ 我确实在我的桌面上连接了Wi-Fi Nano USB适配器，但是不确定它连接的TLS的级别。 我将只强制服务器到TLS1.2并再次检查。 CuxOnthLogLogyEAPTLSV122Nok.tx.Zip 2 K CuxOnthLogLogyEAPTLVS1Y1OK.TXT.ZIP 2.1 K 以上来自于百度翻译 以下为原文 Yes, in that log the TLS handshake fails but that is after the 1st attempt appears to complete ok (line 61) Then line 63 shows the error: wiced_join_events_handler: event_type=0x2e status=0x105 reason=0x20e wiced_join_status=0x16 event = WLC_E_PSK_SUP status = WLC_SUP_KEYXCHANGE reason = WLC_E_SUP_DEAUTH Appears an error with receiving the PMK? whereas the TLS1.1 returns: wiced_join_events_handler: event_type=0x2e status=0x106 reason=0x200 wiced_join_status=0x16 event = WLC_E_PSK_SUP status = WLC_SUP_KEYED reason = WLC_E_SUP_OTHER which completes and acquires and IP address. I included 2 new captures without the retries after the failure. Running a Windows Network Policy Server. I still have to figure out how to capture the EAP handshake on a windows machine? Do you run the wireshark capture on the server? I did connect with a Wi-Fi Nano USB adapter on my desktop but not sure what level of TLS it connected with. I will force the server to TLS1.2 only and check again. |
|
|
|
|
60user192 发表于 2018-11-29 13:16 我验证了爱迪麦斯WiFi Nano确实连接到TLS 1.2（EAP TLS和EAP PEAP）的网络策略服务器，其中包括使用ArrPCAP捕获WiReSARK。 对EAP-PEAP和EAP-TLS（TLSV1.2）进行了失败的WISH.TXT和WiReSARK捕获失败的ISM43362设备的捕获。 EAP-PEAP与TLSV1.0、TLV1.1和TLSV1.2的所有级别都失败。 不确定，但唯一的问题是，在TLS完成后，服务器发送应用程序数据ID＝7，然后应用程序数据ID＝8，而对应用程序数据ID＝7没有响应。 EAP-TLS仅用TLSV1.2失败，Wice设备不响应密钥消息吗？ 我正在使用WICE设备和爱迪麦斯的同一套证书用户名密码。 WiReSARK捕获文件名具有WiFi设备的MAC地址来过滤。 EdixMax WLAN-7LyDaA38，AEYBCY41GEAP-PEAPTLS1L22OK.PCANG.ZIP 550.2 K EdixMax WLAN-7La Daa3qAEYBCY41GEAP-TLS1212OK.PCANG.ZIP 812.7 K WiDeDeDebug Guang-EngEngE-APE-TLS1Y2FAILD.TXT.ZIP 2.1 K WiDeDeCuthOnth.WLAN-AdDr.C4Y7FY51.01O6EAE9EAAP-PEAPTLLS1L22FAIL.PCANG.ZIP 47.3兆字节 WiDeDeCuthOnEngE-APAP-PEAPTLS1L22FAILD.TXT.ZIP 3.5 K WiDeDeCuthOnth.WLAN-AdDr.C4Y7FY51.01O6EAE9EAAP-TLS1212FAILD.PCANG.ZIP 194 K 以上来自于百度翻译 以下为原文 I verified that the EDiMax WiFi Nano does connect to the Network Policy Server with TLS 1.2 (both eap-tls and eap-peap) included the WireShark captures using AirPcap. Inlcuded the debug .txt and WireShark captures of the failing WICED ISM43362 device for both EAP-PEAP and EAP-TLS (TLSv1.2). EAP-PEAP fails with all levels of TLSv1.0, TLSv1.1, and TLSv1.2 Not sure but only issue I see is after TLS completes Server sends App Data ID=7 then App Data ID=8 without a response to App Data ID=7? EAP-TLS only fails with TLSv1.2, WICED device does not respond to the Key message? I am using the same set of certificatesusernamepassword for the WICED device and the EDiMax. The wireshark capture file name has the mac address of the wifi device to filter with.
|
|
|
|
|
asd013 发表于 2018-11-29 13:06 解决了我们的问题与BESL恳求出口的MSK。无法连接到2018网络策略服务器的安全WPA2、企业模式、方法EAP-TLS和EAP-PEAP与TLVS1.2。将问题替换为BESL请求者返回的安全密钥，我们在MbEdTLSyssLyDelvE.KEY（）中计算MSK密钥。包括两个修改文件BestLyHoo.c和SsLytL.c，查找： 你能看一下BESL请求者返回主机的密钥的计算吗？ 根据EAP TLS RCF5216计算MSK密钥 EAP-TLS导出导出密钥材料和参数如下： Kig材料= TLS-PRF 128（Mistar秘密），“客户端EAP加密”， 客户机.随机服务器.随机的 MSK=密钥材料（0，63） EKSK＝KEY材料（64127） IV= TLS-PRF-64（“”，“客户端EAP加密”， 客户机.随机服务器.随机的 运行WSDK SDK2.2.1： 启动VWICEDY0.262.2.0.1.002 [DIPM3IIS43362M3GYL44平台]初始化 [WICEDDYRITOSITIIT ]启动TyReX V5.8 [初始化WiDExNETWorksIIT ] NETXI DUO V5.10Sp3 [创建数据包池] 无线局域网MAC地址：C4:7F:51:02:E2:B3 WLAN固件：WL0: 5月16日2018：00∶27∶03版本5.90.230.31 FWID 01-5849 拉普兰 54.8 K 以上来自于百度翻译 以下为原文 Resolved the problem we are having with the BESL supplicant export of the MSK. Could not connect with security WPA2, enterprise mode, methods EAP-TLS and EAP-PEAP with TLSv1.2 to a 2018 Network Policy Server. Fixed the issue by replacing the security key returned by besl supplicant with the MSK key we calculate in mbedtls_ssl_derive_keys(). Included the two modified files besl_host.c andssl_tls.c, search for: #ifdef FIX_PMK_TLS to find the changes. Can you look into the calculation of the key returned to the host by the besl supplicant? Calculated the MSK key according to EAP TLS RFC5216 EAP-TLS derives exported keying material and parameters as follows: Key_Material = TLS-PRF-128(master_secret, "client EAP encryption", client.random || server.random) MSK = Key_Material(0,63) EMSK = Key_Material(64,127) IV = TLS-PRF-64("", "client EAP encryption", client.random || server.random) Running WICED SDK6.2.1: Starting WICED vWiced_006.002.001.0002 [wiced_platform_init]Platform DPM3_ISM43362_M3G_L44 initialised [wiced_rtos_init]Started ThreadX v5.8 [wiced_network_init]Initialising NetX_Duo v5.10_sp3 [wiced_network_init]Creating Packet pools [wiced_wlan_connectivity_init]WLAN MAC Address : C4:7F:51:02:E2:B3 [wiced_wlan_connectivity_init]WLAN Firmware : wl0: May 16 2018 00:27:03 version 5.90.230.31 FWID 01-5849
|
|
|
|
|
只有小组成员才能发言，加入小组>>
754个成员聚集在这个小组
加入小组2106 浏览 1 评论
1853 浏览 1 评论
3671 浏览 1 评论
请问可以直接使用来自FX2LP固件的端点向主机FIFO写入数据吗？
1786 浏览 6 评论
1536 浏览 1 评论
CY8C4025LQI在程序中调用函数，通过示波器观察SCL引脚波形，无法将pin0.4(SCL)下拉是什么原因导致？
571浏览 2评论
CYUSB3065焊接到USB3.0 TYPE-B口的焊接触点就无法使用是什么原因导致的？
424浏览 2评论
CX3连接Camera修改分辨率之后，播放器无法播出camera的画面怎么解决？
438浏览 2评论
386浏览 2评论
使用stm32+cyw43438 wifi驱动whd，WHD驱动固件加载失败的原因？
916浏览 2评论
/7 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
4315
评论
淘帖
2792
