|
Klemens,
The
problem that you are experiencing is a known bug in the Symbol AP-4131 firmware.
I pestered Symbol in Australia for a fix and managed to get a fixed version of
the firmware on pre-release from the US to test that the problem was fixed. If
you log a support call with Symbol you may also be able to get a copy to test -
firmware version is 3.70-59y. Or use another vendors AP - Cisco 1200 and Orinoco
2000AP both work fine.
The
other problem that you might find is that if you attempt to use a Symbol LA-4121
PCMCIA card under Windows 2000, the driver does not send EAPOL messages to the
AP and hence does not even start the 802.1X authentication
process.
Alternatively I do have some diffs for the FreeRADIUS
source code, that I may have already posted, that change the state processing so
that it works for Symbol APs.
However, based on my experience - I'd use Cisco. It
worked first time and has kept working.
Cheers,
Philip
Blow
Senior Technical Manager Simply Wireless -----Original Message-----
From: Klemens Jaeger [mailto:[EMAIL PROTECTED] Sent: Wednesday, 12 March 2003 1:57 AM To: [EMAIL PROTECTED] Subject: rlm_eap: State verification failed hi!
do I need the module "files" in radiusd.conf where
the file "user" will be implemented? or is the module eap enough?
thanks,
kle
|
Title: Message
- rlm_eap: State verification failed Klemens Jaeger
- Re: rlm_eap: State verification failed Artur Hecker
- rlm_eap: State verification failed Klemens Jaeger
- Re: rlm_eap: State verification failed Artur Hecker
- rlm_eap: State verification failed Klemens Jaeger
- Re: rlm_eap: State verification failed Artur Hecker
- rlm_eap: State verification failed Klemens Jaeger
- Re: rlm_eap: State verification failed Artur Hecker
- rlm_eap: State verification failed Klemens Jaeger
- rlm_eap: State verification failed Philip Blow
- rlm_eap: State verification failed Klemens Jaeger
