Hello Everyone - I have received a number of questions recently regarding the extended Radius request known as "Disconnect-Request", so here is some important information. The first thing to understand is that, as always, the Radius protocol is implemented in a client/server architecture, in which the client sends requests to the server. Note that there is no mechanism in the protocol for a server to send a request to a client. This is important to understand, because for a "Disconnect-Request" to be handled by a NAS, the NAS itself must be configured to act as a Radius server for the purposes of this request at least (as well as being a Radius client in the usual sense). Now clearly, in more common utilisation, the NAS is the client and Radiator is the server, so for this to be supported by the NAS, it is the NAS software that must support the function. Further, the exact syntax to specify which session to terminate is also NAS dependent. So what does this mean for Radiator? Well, firstly, Radiator itself does not necessarily need to be involved at all (unless you want to log these requests, which is probably a good idea). If you do want the "Disconnect-Request" packets to transit Radiator, you will need to set up at the very least an AuthBy RADIUS proxy clause to forward the request to the NAS. You may also want to configure a special Realm or Handler which will limit what system hosts are allowed to send "Disconnect-Requests" at all. Note that all of the above does not say anything about what software you need to actually generate the "Disconnect-Request" packet. As I have mentioned previously, you can use the latest version of "radpwtst" with the "-code Disconnect-Request" parameter, however please understand that the exact syntax of the rest of the packet is NAS dependent, and you will need to get the details from your vendor. If anyone has details of a successful "Disconnect-Request" implementation, we will be glad to add an item to the FAQ. regards Hugh -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
