I have tried to connect the WL1271 in WPA Enterprise mode.I am not able to connect in WPA Enterprise mode.
whether WL1271 chipset solution will support WPA Enterprise Mode or not ?
Enterprise normally requires additional feature components not supported in the OMAP35x+WL1271 platform, such as Cisco CCX extensions. Although the WL1271 device itself does support Enterprise, the software that accompanies the platform does not provide support for that. We don't plan to support this feature currently but will monitor the market demand for it.
CB, I'm surprised by your answer. WPA-Enterprise and WPA2-Enterprise refer to not using a preshared key (PSK) but instead relying on a radius server (or similar) or key derivation. This is a Wi-Fi (or 802.11i) standard and has nothing to do with CCX (except for the fact that CCX mandate those standard capabilities be available).
do you mean to say thaw neithe WPA-Enterprise not WPA2-Enterprise are supported by the TI driver?
WPA2-Enterprise is becoming quite common, consumer level products now start supporting it. WPA-Enterprise is a little weird, if you're going to go to the trouble of providing a radius server, chances are you'll want to use more solid (AES) security, but I'm not sure why the driver would care.
I could have sworn someone on my team had WPA2-Enterprise (using PEAP/Mschapv2) working on the Mistral EVM., I'll check with him. I see that Janardhan has several other posts in this forum indicating that he is running into problem with WPA2-Enterprise also, so maybe it truly is not supported.
TI WLAN driver supports WPA enterprise but it was not tested on this platform, it will be tested in the next release
What about enterprise support in the Windows CE driver?
Yes we do plan to have enterprise support on WinCE with our next WinCE release. it will be available on AM3715 EVM with support to 1271 (bgn band support)
One more question - is the enterprise now available in the Linux driver and if so which version? It is ambiguous in the other posts what the "next release" is that will support it.
We do have enterprise support (EAP/TLS WPA,WPA2) with our latest linux release.
please download the latest package from the WiKi page in address: http://processors.wiki.ti.com/index.php/ARM_Processor_Wireless_Connectivity_Downloads please download release SW-0005.
I have some questions about CCX support.
We will do CCX-V4-test by using WL1273L and WLAN driver (Ver. M6) for WinCE6.0.
We want to know which item nubmber of CCX test the combination supports originally.
If youhave any documents about support items list for CCX, could you privide them to me.
Which WinCE supplicant are you working with for CCX?
As you know MS Zero config doesn't support any of the EAP-LEAP/EAP-FAST and fast-raoming (CCKM).
The driver with CCX patches (That i'm sure you have) knows how to handle messurments and tspecs.
Also it include entry point for CCKM and rouge APs.
But the majority of the CCX-v4 support cases is outside of the driver.
- Elad Raz
> Which WinCE supplicant are you working with for CCX?
We are using 3rd part supplicant instead of WZC.
The supplicant suppprt them.
We have a list which shows support item number by WLAN driver (Ver. M5).
Do you have a support list for CCX-V4's items by original WLAN driver (Ver. M6)?
Dear Mr Tatsuya,
We tested with devicescape supplicant and with our own modified open-source wpa-supplicant CCKM enabled.
We have passed CCX certificate for TI WinCE driver for all Azimuth tests require. The testing result document is not public so I'm not sure that I can share it with you. But tests included tspecs, eap-leap/eap-fast, CCKM TKIP and CCKM AES.
Do you have any specific test you have problem with?
Hope I could help a little.
> Do you have any specific test you have problem with?
We will start to do CCX-certificate at Allion-lab from this month.
We want to know whether the latest WLAN driver (Ver. M6) for WinCE6.0
can pass CCX-V4 before oue test. After our test, we willl compare between
your result and our one.
Dear Mr Tatsuya,
I'm not sure which version of WinCE do you have, since the public M6 driver doesn't have any CCX files (Needs to sign agreement with Cisco).
And I know that M6 driver with CCX don't have any of the devicescape CCKM API to integrate with supplicant (Start-cckm, add rouge ap, etc..)
We port MCP 2.5 driver and added the CCX features into it.
You are more then welcome to contact me directly. My email appears in my profile page
Is there still an open issue, please note that TI does not have WiNCE offering therefore not supporting it directly. WiNCE can be supported by third party.
Thank you for your cooperation.
This issue will be solved by ourselves.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.