Hello Aaron -
On Thu, 28 Oct 1999, Aaron Holtz wrote:
> Hello - I've got a Handler that looks at the Nas-IP-Address to determine
> what to do. I've also got a bad nas that doesn't send Nas-IP-Address in
> the access packet. I used to have a preclienthook to set this up, but
> that is now built into radiator. I've put a log statement in the getNasId
> and the last statement that is supposed to fix this is indeed working.
> However, my Handler isn't being matched. From Trace 4:
>
>
> Wed Oct 27 12:25:27 1999: DEBUG: Packet dump:
> *** Received from 111.111.49.2 port 1536 ....
> Code: Access-Request
> Identifier: 181
> Authentic: r<23><198>~#<18>~_&e 4<255>_Yp
> Attributes:
> User-Name = "usera"
> Password = "<254>a%G<225><10>d<218>OW<186>!<28><159>cT"
> Service-Type = Framed-User
> Framed-Protocol = PPP
> NAS-Port = 9
>
> Wed Oct 27 12:25:27 1999: DEBUG: Check if Handler
> NAS-IP-Address=/111.111.(49|59).2/, Service-Type=Framed-User should be
> used to handle this request
>
The problem, as you say, is that "NAS-IP-Address" is not present as an
attribute in the packet - herefore your Handler won't match as it is looking
for that specific attribute.
A better way to do this is to match on Client-Id:
<Client some.client>
...
</Client>
<Handler Client-Id = some.client>
....
</Handler>
Have a look at Section 13.1.15 in the manual.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
