Thanks for the quick response! The problem was with the NAS code. > My question is why and how are you changing the > length of the CHAP-Challenge?
On the CHAP side the NAS gives the client a random sized challenge and somehow only authentications where the chap_challenge was 16 octets were going through and others were resulting in a reject. > FreeRADIUS has *no* code in it which depends on > the length of the > CHAP-Challenge. If there isn't a CHAP-Challenge in > the packet, then > it's taken from the request authenticator, and MUST > be 16 octets. > The CHAP-Challenge attribute can be almost any > length, and that's > the way the 'verify challenge' code works. You are right. Its working for the other values too! Thanks again, Puneet __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
