Can freeradius handle a Disconnect Request (Attribute 40). If so how ? �This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.aspx "
When will it be able to? jay At 10:48 AM 10/13/2005, you wrote:
"Ashwin Gobind" <Ashwin.Gobind@vodacom.co.za> wrote:
Can freeradius handle a Disconnect Request (Attribute 40).
No.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Jay Barnell <jbarnell@barnellts.com> wrote:
When will it be able to?
When a patch is sent in. As always, patches are welcome. "radclient" can *send* those packets, but the server can't receive them. Why? Read the RFC's for how those packets are supposed to be implemented. When a server receives a disconnect packet, it has to check to see IF it had an Access-Request with the same contents, WOULD that request be forward to the IP that the disconnect request came from. That's hard. It's easier to punt on the problem. We could implement limited support for disconnect, where local administrators (not remote ones) would be allowed to send disconnect packets. But if that's the requirement, those admins can already use "radclient" to send packets directly to the NAS. So I'm not sure there's *any* benefit to adding disconnect support to the server. Alan DeKok.
participants (3)
-
Alan DeKok -
Ashwin Gobind -
Jay Barnell