Not able to connect Cisco Aironet AP in 2.4 GHz

Ask the Community
Close
Ask the Community
nav search Icon
Forums gray-arrow gray-arrow
Resources gray-arrow gray-arrow
About gray-arrow gray-arrow
Groups gray-arrow gray-arrow
nav-user Account

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
Log in arrow right alert

Not able to connect Cisco Aironet AP in 2.4 GHz

aktac_3789331
Level 2
Level 2
‎Oct 18, 2018 07:07 AM
‎Oct 18, 2018 07:07 AM
Jump to solution

Hello,

I am evaluating the cypress CYW943907AEVAL1F module. And I am using the SDK version 6.0.1.5. I am using a tcp_client example and tried to connect to the Cisco AP. I am not able to connect to the AP neither in security mode nor in the open mode. I took the wireless captures and observed the basic association process also did not start. then I used the snip. scan example from the SDK to see whether the AP is updated in scan list and not seen the AP in the list. But I  was able to connect the same AP in 5 GHz with open and WPA2 security.

Moreover, Mobile devices were able to connect to the same Cisco AP in 2.4 GHz so the AP seems to be proper in connection wise.

I am attaching the captures here FYR. As per the captures, probe response was seen every time  for the probe request from the cypress module.

Can anyone please explain me this behavior.

Thanks

Akash

cypress_no_assoc.pkt.zip
0 Likes
Subscribe
1 Solution

Re: Not able to connect Cisco Aironet AP in 2.4 GHz

PriyaM_16
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted
‎Dec 25, 2018 04:47 AM
‎Dec 25, 2018 04:47 AM
Jump to solution

Hello,

Please add the extended params in the wiced_wifi_scan_networks() as below:

wiced_result_t wiced_wifi_scan_networks( wiced_scan_result_handler_t results_handler, void* user_data )

{

  const wiced_scan_extended_params_t extparam = { 5, 110, 110, 50 };

 

  return wiced_wifi_scan_networks_ex( results_handler, user_data, WICED_SCAN_TYPE_ACTIVE, WICED_BSS_TYPE_ANY, NULL, NULL, NULL, &extparam, WICED_STA_INTERFACE );

}

This is a workaround if you not able to scan cisco APs. The extended scan parameters overwrites the default firmware parameters with a higher value for scanning. For example: The default number of probes in firmwareis 2. This is increased to 5 through extended scam params.

View solution in original post

7 Replies