Hello Arjen -
On Fri, 10 Mar 2000, Glasshouse Beheer wrote:
> Hi!
>
> Does Open Systems plan to implement the radius packet codes 12 & 13 in the
> near future?
> According to RFC2138 these are meant for Status-Server & Status-Client tho
> both are experimental and not further documented.
>
> Personally I would like to be able to send the radius server a such packet
> and get a response about the status of the server back.
>
> At the moment I have a piece of perl code running that sends the radius an
> empty Access-Request packet every so often. This is just to check if
> Radiator is actually running. A Status-Server packet would probably be much
> better for this.
>
Status-Server has always been supported and in Radiator 2.15 we have modified
its behaviour to deal with per Client statistics in a configurable manner. Have
a look at section 6.4.14 in the Radiator 2.15 reference manual. You can also
use radpwtst to send a Status-Server request - section 8.0 in the manual.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
