Hi
I am having a problem getting Radiator to work with my Handler setup.
We want to Auth people differently depending on their Called-Station-Id
attribute but when I configure it, Radiator seems to just pick the first
Handler I define and use it.
Here is part of the config:
<Handler Called-Station-Id=32800000>
<AuthBy DBFILE>
Filename %D/users.permanent
</AuthBy>
</Handler>
<Handler>
<AuthBy DBFILE>
Filename %D/users.standard
</AuthBy>
</Handler>
Here is a sample from the logfile at trace level 4:
Code: Access-Request
Identifier: 139
Authentic: blah...
Attributes:
NAS-IP-Address = X.X.X.X
NAS-Port = 81
NAS-Port-Type = Async
User-Name = "test"
Called-Station-Id = "32800300"
Calling-Station-Id = "XXXXXXXX"
User-Password = "XXXXXXXX"
Service-Type = Framed-User
Framed-Protocol = PPP
Mon Mar 1 16:56:15 1999: DEBUG: Check if Handler Called-Station-Id =
"32800000" should be used to handle this request
Mon Mar 1 16:56:15 1999: DEBUG: Handling request with Handler
'Called-Station-Id = "32800000"'
Mon Mar 1 16:56:15 1999: DEBUG: Handling with Radius::AuthDBFILE
Mon Mar 1 16:56:15 1999: DEBUG: Radius::AuthDBFILE looks for match with
test
Mon Mar 1 16:56:15 1999: INFO: Access rejected for test: No such user
This should have skipped the first handler as the Called-Station-Id doesn't
match and gone to the second one which is the catch-all case for our normal
dialup number.
Can anyone see what the problem is?
--
Stacy Horton
System Administrator
Global Info-Links
[EMAIL PROTECTED]
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
