"Gil Yu" <[EMAIL PROTECTED]> wrote: > THanks for your response, but there is no information on the > Status-Server.
Exactly. Its use is implementation-dependent. > What I would like is something to indicate what the status of the > server is (from the RADIUS client perspective). See the link I posted about 'Keep-Alives'. If the server is down, what can the client do? Nothing. So there's no point in checking. If the client is performing authentication requests, then it will notice that the server is down, when the server doesn't respond. So Status-Server is pointless. If the client is NOT performing authentication requests, then it doesn't care if the server is down. So there's no point in using Status-Server. > Any suggestions? First, I would like to know why you would like to use Status-Server, and how you think it would help. Personally, I'm opposed to using Status-Server, because it's pointless, as the 'Keep-Alives' section says in the RFC. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
