Hi again,
I don't want to add another proxying principle as the current one fullfill my requirement, but I don't see why you should drop packet not containing a User-Name field. From my point of view it should fall in the NULL , or the DEFAULT case (same way as packet not containing a realm) can you explain me a little bit more why you think that those packet should be drop.
No, you are correct. The RFC specifies 0 or 1 instances of User-Name. The server *should* still proxy to a DEFAULT or NULL if there is not a User-Name attribute present.
The proxy code is based on looking for a 'realm' which is parsed from the 'User-Name' attribute. However, DEFAULT and NULL are still valid, and as you state the RFC does not require User-Name for Accounting, though it does for Authorization ( very helpful from the RFC folks, *sigh*, gotta love the consistency ).
I'll take a look at the code to correct the behaviour in the current CVS.
-Chris -- \\\|||/// \ StarNet Inc. \ Chris Parker \ ~ ~ / \ WX *is* Wireless! \ Director, Engineering | @ @ | \ http://www.starnetwx.net \ (847) 963-0116 oOo---(_)---oOo--\------------------------------------------------------ \ Wholesale Internet Services - http://www.megapop.net
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
