"Derek M. Harkness" wrote: > Thanks for the help! Here is my log (radiusd -X), this was captured on > a linux and I haven't had a chance to apply the patch yet, but I will. > Thanks, again. >
Its just one line change from int to unsigned short. Let me know your findings with the patch. > Sending Access-Challenge of id 90 to 141.215.3.48:1126 > Service-Type = Framed-User > EAP-Message = > "\001Z\000\026\004\020J\347\0236\344K\371\277y\322u.#H\030\245" > Message-Authenticator = 0x00000000000000000000000000000000 > State = > 0xbb127c33d668ec1725a862f2e3195975dd599a3c9bbbfc5c5148b09728212c51e3dd3138 > Finished request 0 > Going to the next request > --- Walking the entire request list --- > Waking up in 6 seconds... > --- Walking the entire request list --- > Cleaning up request 0 ID 90 with timestamp 3c9a59dd > Nothing to do. Sleeping until we see a request. > Server sent the Access-Challenge, but never received any response from the AP. Most likely some configuration issue at the AP/supplicant. -Raghu - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
