At 08:14 AM 1/21/00 +1100, Hugh Irvine wrote:
> > . Some of my nas are sending Accounting requests that
> > have no Username attribute. Now they are getting forwarded to our default
> > (gric) radius server, but i want to handle them differently. Can i
> define a
> > Handler entry to catch them? (with no Username attribute as its criteria)
> >
>
>Yes - do something like this:
>
><Handler User-Name = "">
> <AuthBy ....>
> ....
> </AuthBy>
></Handler>
>
>The usual caveats apply regarding not mixing Realms and Handlers in the same
>configuration file, and place the more specific Handlers before the more
>general.
I tried it but i didnt work. It is still falling through the last <Handler>
(default) entry. Remember that the User-Name attibute is not null, but missing!
Here is a part of the log
*** Received from 172.16.2.31 port 1904 ....
Code: Accounting-Request
Identifier: 4
Authentic: n];n<1><14>2x<15>C4<18>_E<13>q
Attributes:
Acct-Status-Type = Accounting-On
Acct-Reason = ""
Acct-Delay-Time = 18000
Acct-Session-Id = "This is an Accounting ON message"
NAS-IP-Address = 200.xx.yy.zz
NAS-Identifier = "200.xx.yy.zz"
Proxy-State = 2
Fri Jan 21 19:55:57 2000: DEBUG: Handling request with Handler 'Realm=DEFAULT'
Fri Jan 21 19:55:57 2000: DEBUG: Deleting all sessions for 200.xx.yy.zz
Fri Jan 21 19:55:57 2000: DEBUG: Handling with Radius::AuthRADIUS
Fri Jan 21 19:55:57 2000: DEBUG: Packet dump:
*** Sending to 172.16.1.32 port 7001 ....
Code: Accounting-Request
Identifier: 241
Authentic: <0><0><0><0><0><0><0><0><0><0><0><0><0><0><0><0>
Attributes:
(...)
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
