WPS注册者支持WPS1和WPS2标准，WEP不受WPS2规范的支持。
其他两种模式没有测试WPS2认证，所以WICE以前没有专门支持过它们。
我们可以在这里重新创建这个问题，从控制台日志看来，当密码是AES时，凭证被解析为WPA2，当密码为TKIP时作为WPA解析，或者AP在凭证中放置错误的信息。由于安全类型不正确，任何方式都无法加入。我们将调查这个问题，以解决这个问题在未来的SDK版本。
以上来自于百度翻译
以下为原文
The WICED WPS enrollee supports the WPS1 & WPS2 standard, WEP is not supported by the WPS2 specification.
The other two modes are not tested for WPS2 certification so WICED has not specifically supported them previously.
We can recreate the issue here and from the console log it appears to be that the credentials are either parsed as WPA2 when the cipher is AES and as WPA when the cipher is TKIP, or the AP is putting the wrong information in the credentials. Either way WICED cant join because the security type is incorrect. We will investigate this with a view to addressing this issue in a future SDK release.
WPS注册者支持WPS1和WPS2标准，WEP不受WPS2规范的支持。
其他两种模式没有测试WPS2认证，所以WICE以前没有专门支持过它们。
我们可以在这里重新创建这个问题，从控制台日志看来，当密码是AES时，凭证被解析为WPA2，当密码为TKIP时作为WPA解析，或者AP在凭证中放置错误的信息。由于安全类型不正确，任何方式都无法加入。我们将调查这个问题，以解决这个问题在未来的SDK版本。
以上来自于百度翻译
以下为原文
The WICED WPS enrollee supports the WPS1 & WPS2 standard, WEP is not supported by the WPS2 specification.
The other two modes are not tested for WPS2 certification so WICED has not specifically supported them previously.
We can recreate the issue here and from the console log it appears to be that the credentials are either parsed as WPA2 when the cipher is AES and as WPA when the cipher is TKIP, or the AP is putting the wrong information in the credentials. Either way WICED cant join because the security type is incorrect. We will investigate this with a view to addressing this issue in a future SDK release.
举报
