It is not supported. We support wifi direct instead. Or you can use soft AP mode. But the classic ad-hoc mode is not supported and will never be since it is not supposed to be used and most use cases are better served by wifi direct instead.
Thanks, this helps!
Why is it that you say that ad.hoc is not supposed to be used?
It solves a whole range of mesh related problems that AP/STA does not.
And WiFi-Direct is P2P, slow to set-up and prone to implementation differens issues.
Please use that little extra time to make ad-hoc work. You are so close.
Wow, it's been a very long time since I've been asked about adhoc!!!
From memory, we supported this for legacy 11b connections but it was no longer mandatory to support on later WLAN standards, mostly because the wpa2 security was not implemented on these links.
I'll double check when I get back to my room after embedded world today
Sent from my iPhone
1 of 1 people found this helpful
Did you find any thing out?
Any progress will be appreciated.
What I have found out this fare:
The BCM43362 is able to connect to a AD-HOC network if one is in range. ( I might have changed something in WICED to get there but not that much.)
The BCM43362 is not able to answer when requested when it is in AD-HOC mode.
If there is not any matching AD-HOC nodes in range when the BCM43362 tries to connect it will make up a new IBSS id even if one is given in the connect request. (Look at wiced_join_ap_specific ignores BSSID )
I have rechecked here and can confirm that adhoc mode is *not* supported in the WICED SDK and we have no plans to implement it as this would be a proprietary implementation and likely to lead to interoperability issues.