Hello M.McNeil,
I've tried it also, but after upgrade of WLSE to a new version it
stopped working. Then I've configured the same AP (AP1231G) that I'm
using as WDS master with the local RADIUS server for LEAP
authentication and configured FreeRADIUS to proxy all the requests of
WDS/WLSE
On Thu, Aug 11, 2005 at 07:02:19PM -0400, Alan DeKok wrote:
[EMAIL PROTECTED] wrote:
I am trying to speak between my Freeradius server and a Cisco WLSE.
I am seeing EAP timeouts while WLSE is trying to authenticate
through Freeradius.
Short summary: the supplicant is broken.
[EMAIL PROTECTED] wrote:
I am stuck using WLSE. Are there plans on an official fix in Freeradius,
to work with whatever is broken in WLSE?
As I said:
it's changing the EAP ID in a broken way, which means that the AP
doesn't add the State attribute from the previous challenge.
Fixing
Hello,
I am having an issue getting Cisco's WLSE 2.11 to successfully
authenticate with FreeRadius 1.0.4. I read where Alan DeKok stated that
the supplicant is broken, and was wondering if this is something Cisco
has to fix with the WLSE? or is there a way for me to fix the
supplicant?
I am trying to speak between my Freeradius server and a Cisco WLSE. I am seeing
EAP timeouts while WLSE is trying to authenticate through Freeradius.
I have setup the AAA details (server,port,username,password,eap protocol) in
the WLSE, and enabled fault tracking, so that polling is able to take
5 matches
Mail list logo
