I've configured both the RADIUS server and verifies EAP-TLS authentication via clients. This is however not 802.1x, I want to make the device work with 802.1x via the air to route clients properly. However as it is now, I am unsure on how to configure the device. I see many references in the documentation to set the mode to WEP and 802.1x for the SSID. I only have no encryption, WPA-Personal and WPA-Enterprise from the dropdowns. Adding in the 802.1X supplicant information (username, passord and .pem certificate from the CA with private key) did not change behaviour.
Thoughts on what I might be missing to get it working?
I worked some on this issue over the weekend and I think I resolved it in a proper manner.
The 802.1x supplicant information on the WAP321 is to enable it to access already 802.1x enabled ports on a switch, ie its itself a device.
The WPA2-Enterprise is what one defines as (one of) the wireless network(s), with a properly configured RADIUS server, it will hand out and override any VLAN's in the air for the client on a per-device basis. This was the "revelation" that led me to the conclusion that enabling 802.1x over the air in the documentation is misleading in regards to the Open with 802.1x setting which is not available for selection on my WAP321.
With the latest release of firmware for the WAP 561, 551, 371, 351 a new
feature was added that would allow customers to upgrade the firmware for
their clustered access points from the main access point.The basic steps
to accomplish this is:1) Download th...
Special thanks to Alex McDonald for sharing his favorite tip:My favorite
tip is the ‘write default’ command on autonomous wireless access points,
it simplifies manual conversion of a WAP with a static ip address to a
LAP with a DHCP address.This saved a l...