Specifications

OmniAccess Reference: AOS-W System Reference
606 Part 031652-00 May 2005
RADIUS Server reports “Authentication Method Not Supported”
This error message is caused by the client and server using different 802.1x
authentication methods.
z Verify that the RADIUS server and client are configured for the same 802.1x
authentication method. For example, if the RADIUS server is configured to
use PEAP, the client must also be configured this way. Microsoft clients
default to EAP-TLS (Smart card or other certificate).
Client stops communicating after roaming (WPA)
In a network running WPA/TKIP, the NIC card may fail to re-negotiate
encryption keys after roaming to a new AP. This behavior will manifest itself
as the client continuing to hold an active association, but unable to
communicate to the network. Resetting the NIC card will clear the problem.
z This problem has been seen with Proxim Orinoco A/B/G cards with driver
version 2.4.2.17. After roaming to a new AP, the client will generate MIC
(Message Integrity Check) failures during phase 2 of the 4-way WPA key
exchange handshake.
z Verify the problem by enabling 802.1x debugging on the Alcatel switch:
(config) # logging console debug
# debug authmgr dot1x dot1xtrace
VPN
VPN Dialer displays “Interface is down or no route”
This message indicates that the client does not have an IP address or a route
to reach the Alcatel switch. To view the IP address and default gateway for
the client, click the “Network Info” button in the VPN dialer.
z If there is no IP address on the interface, verify that the interface is config-
ured to obtain an address via DHCP.
z Verify that association to the wireless network succeeded. Examine the
output of “show user” on the Alcatel switch to view the client’s associa-
tion state.
z Verify that the DHCP server is active. If the Alcatel internal DHCP server is
in use, the command “show log dhcp” will provide information on DHCP
server activity.