Triggering a Disconnect-Request
I know I can use radclient to send a disconnect message to a NAS. Is there any way to trigger the FreeRADIUS process to send a disconnect message instead? In my case, I have a FreeRADIUS server running happily, and an external script that sends disconnects. Right now, the script runs alongside FreeRADIUS on the same server. I would like to move that script elsewhere, but I would like to offload it to another server. Problem is, the NAS only honors requests from known RADIUS servers. If it receives the request from anywhere else, it is simply ignored. Ideally, my script would send some sort of message (something like a status message) that FreeRADIUS would turn around into a disconnect request. Any ideas? Thanks Norman
How does your external script send the disconnects? alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Norman Elton wrote:
I know I can use radclient to send a disconnect message to a NAS. Is there any way to trigger the FreeRADIUS process to send a disconnect message instead?
Sure. See raddb/sites-available/originate-coa.
Ideally, my script would send some sort of message (something like a status message) that FreeRADIUS would turn around into a disconnect request.
Uh... you could send FreeRADIUS a Disconnect-Request message. And configure FreeRADIUS to proxy it to the NAS. That will work. See raddb/sites-available/coa recv-coa { ... update control { Home-Server-Pool := nas } ... } You will have to set up a home server && home server pool for the NAS. This is because the CoA port is 3799, not 1812. And, the NAS is acting like a home server in *receiving* packets, instead of *originating* them. It's a bit annoying, but it follows the same proxy configuration as normal packets. Perhaps in a future version we could just add "proxy to client" functionality. Alan DeKok.
participants (3)
-
Alan Buxey -
Alan DeKok -
Norman Elton