> Please can anyone suggest me the following: > > If an AP is to be built, then what are the essential > requirements > that it has to support in order to be able to support 802.1x/EAP-Types(TLS, > MD5) > Authentications with RADIUS server as the Authentication server.
At this point, if you're building an AP, it should be made to work with *any* EAP type. This is trivial to do -- there is no special work to support EAP-TLS vs. EAP-MD5, etc. Given that WPA-enabled APs will be coming out soon, I'd also recommend that you support the full WPA specification available from WiFi Alliance, including the new EAPOL-Key packets and TKIP ciphersuite. > Actually what mechanism is to be followed for the 802.1x/EAP-TLS > authentication using RADIUS. Have a look at the following documents, both of which will be in IETF last call soon: http://www.ietf.org/internet-drafts/draft-congdon-radius-8021x-22.txt http://www.ietf.org/internet-drafts/draft-aboba-radius-rfc2869bis-08.txt (This should be available early next week). If you have questions that aren't answered by those specs, please send email to the authors and the EAP WG mailing list ([EMAIL PROTECTED]). You also probably want to implement the revised IEEE 802.1X specification in progress, IEEE 802.1aa, rather than IEEE 802.1X-2001, since it fixes lots and lots of bugs. This can be obtained from the IEEE 802.1 archive. Also, please look at the revised EAP specification, RFC 2284bis: http://www.ietf.org/internet-drafts/draft-ietf-pppext-rfc2284bis-10.txt Again, lots of bug fixes and clarifications here. -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
