> normally, you should post the whole log, the configuration of the client
> (intel-AP) and of the concerned users, since otherwise it's generally
> difficult to understand what's wrong.
Here is the  freeradius log:
(Intel AP has no special options for this i think,
and for users configuration i use just this:
DEFAULT         Auth-Type := EAP
                Fall-though =1,
                Session-Timeout = 300
)

Listening on IP address *, ports 1812/udp and 1813/udp.
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.1.100:1024, id=101,
length=127
        User-Name = "usr003002"
        NAS-IP-Address = 192.168.1.100
        Called-Station-Id = "00053C059AB0"
        Calling-Station-Id = "00053C058A96"
        NAS-Identifier = "WDAP5000"
        NAS-Port = 1
        Framed-MTU = 1400
        NAS-Port-Type = Wireless-802.11
        EAP-Message = "\002d\000\016\001usr003002"
        Message-Authenticator = 0x9706af79e630a5818c3fe04326a0652a
modcall: entering group authorize
  modcall[authorize]: module "preprocess" returns ok
  modcall[authorize]: module "eap" returns updated
    rlm_realm: No '@' in User-Name = "usr003002", looking up realm NULL
    rlm_realm: No such realm NULL
  modcall[authorize]: module "suffix" returns noop
    users: Matched DEFAULT at 152
  modcall[authorize]: module "files" returns ok
modcall: group authorize returns updated
  rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
modcall: entering group authenticate
rlm_eap: processing type tls
  modcall[authenticate]: module "eap" returns ok
modcall: group authenticate returns ok
Sending Access-Challenge of id 101 to 192.168.1.100:1024
        EAP-Message = "\001e\000\006\r "
        Message-Authenticator = 0x00000000000000000000000000000000
        State =
0x117eff12bb3702ad6348dd7b6b4345687a0f913de21e2f3af1d9e61acc8a95bbdc4ff478
Finished request 0
Going to the next request
--- Walking the entire request list ---
Waking up in 6 seconds...
rad_recv: Access-Challenge packet from host 192.168.1.100:1024, id=101,
length=84
Reply packet code 11 sent to a non-proxy reply port from client
intel-AP:1024 - ID 101 : IGNORED
rl_next:  returning NULL
Waking up in 6 seconds...
rad_recv: Access-Challenge packet from host 192.168.1.100:1024, id=101,
length=84
Reply packet code 11 sent to a non-proxy reply port from client
intel-AP:1024 - ID 101 : IGNORED
--- Walking the entire request list ---
Waking up in 4 seconds...
--- Walking the entire request list ---
Cleaning up request 0 ID 101 with timestamp 3d910f7a
Nothing to do.  Sleeping until we see a request.


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to