Anonymous
Not applicable
Mar 25, 2013
06:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:28 PM
[WICED-SDK-2.2.1]
We are attempting to connect with a router through WPS without having to modify the DCT, and thus are using the low-level wiced_wifi_join().
Our code uses wiced_wps_enrollee() to find APs and wiced_wifi_join() to join them.
join() returns WICED_SUCCESS, and wiced_network_is_up(WICED_STA_INTERFACE) returns TRUE immediately after joining.
Subsequent code that attempts to use this interface, however, fails at the link check stage.
For example, wiced_udp_create_socket() returns -4 (WICED_NOTUP).
When we instead hardcode this access points credentials and use wiced_network_up(), we do not run into any issues.
What steps do we need to take before/after wiced_wifi_join() to bring up our connection?
Labels
- Labels:
-
Security
- Tags:
- [wiced-sdk-2.2.1]
- access
- attempting
- attempts
- beforeafter
- bring
- check
- code
- connect
- connection
- credentials
- establish
- fails
- find
- hardcode
- immediately
- interface
- issues
- join
- joining
- link
- low-level
- modify
- points
- returns
- router
- stage
- steps
- subsequent
- true
- wiced_network_is_upwiced_sta_interface
- wiced_network_up
- wiced_notup
- wiced_success
- wiced_udp_create_socket
- wiced_wifi_join
- wiced_wps_enrollee
- wps-discovered
6 Replies
Anonymous
Not applicable
Mar 25, 2013
06:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:29 PM
There are two parts to bring up the connection, the first is the Wi-Fi link and the second is the IP layer. If you look at wiced_network_up() you will see the steps required after wiced_wifi_join().
Anonymous
Not applicable
Mar 25, 2013
06:29 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:29 PM
Thanks. How can I perform this IP layer initialization without morenetworking stack-dependent calls from my application?
Anonymous
Not applicable
Mar 25, 2013
06:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:30 PM
The IP initialization is unique to each network stack and is the reason why we have created wiced_network_up().In what way is wiced_network_up() not suitable for your needs?Can we improve the API or do you have unique requirements?
Anonymous
Not applicable
Mar 25, 2013
06:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:30 PM
Unfortunately, wiced_network_up() relies on wiced_join_ap(), which gets itsaccess point info from the DCT. Im trying to join a WPS-identified access point without first placing that access point in the DCT. I was hoping there would be a way to avoid this complexity.If using the DCT is unavoidable with the current API, we will just use theDCT. I dont think our use case is significant enough to warrant an APIaddition.
Anonymous
Not applicable
Mar 25, 2013
06:31 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 25, 2013
06:31 PM
You can easily create a copy of wiced_network_up() and then customize it to provide the functionality you need.
Anonymous
Not applicable
May 28, 2014
11:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 28, 2014
11:21 AM