Re: RFC 3576 support

2008-04-13 Thread Alan DeKok
Arran Cudbard-Bell wrote: New identifiers are assigned when forwarding RADIUS packets anyway (i'm guessing), so there's no problem with conflicts between remotely generated and locally generated CoA messages. Yes. So in your implementation, we'll be able to fork off a CoA request on

Re: RFC 3576 support

2008-04-12 Thread Arran Cudbard-Bell
Alan DeKok wrote: Arran Cudbard-Bell wrote: Ok take eduroam for example. A change in user authorisation at their home site may result in the generation of a CoA request for the user to be disconnected at the remote site, this would be proxied by the remote sites RADIUS server. That same server

RFC 3576 support

2008-04-11 Thread vmx vmx
information on the site on how ro configure this. From this it appears only a test client RadClient is supporting this: http://www.usenet-forums.com/freeradius-users/280002-re-change-authorization.html Is there any development? Has RFC 3576 support has been introduced for Server

Re: RFC 3576 support

2008-04-11 Thread Arran Cudbard-Bell
-authorization.html Is there any development? Has RFC 3576 support has been introduced for Server and not for client. I want to send CoA and DM form the server. Thank you - List info/subscribe/unsubscribe? See http

Re: RFC 3576 support

2008-04-11 Thread Arran Cudbard-Bell
Alan DeKok wrote: Arran Cudbard-Bell wrote: FreeRADIUS does not currently support 3575, it's on the development roadmap. When support is added to the server core it will only be for *proxying* CoA messages not generating them. You can generate your own CoA messages using the radius client

Re: RFC 3576 support

2008-04-11 Thread Alan DeKok
Arran Cudbard-Bell wrote: Ok just the asynchronous nature of CoA requests... It's not really the servers job to process feedback from the various SNMP probes, IDS's , or track changes in the authorisation of users or their equipment. Yes. That's what proxying is for. I guess I can see

Re: RFC 3576 support

2008-04-11 Thread Alan DeKok
Arran Cudbard-Bell wrote: FreeRADIUS does not currently support 3575, it's on the development roadmap. When support is added to the server core it will only be for *proxying* CoA messages not generating them. You can generate your own CoA messages using the radius client bundled with the

Re: RFC 3576 support

2008-04-11 Thread Arran Cudbard-Bell
Alan DeKok wrote: Arran Cudbard-Bell wrote: Ok just the asynchronous nature of CoA requests... It's not really the servers job to process feedback from the various SNMP probes, IDS's , or track changes in the authorisation of users or their equipment. Yes. That's what proxying is

Re: RFC 3576 support

2008-04-11 Thread Alan DeKok
Arran Cudbard-Bell wrote: Ok take eduroam for example. A change in user authorisation at their home site may result in the generation of a CoA request for the user to be disconnected at the remote site, this would be proxied by the remote sites RADIUS server. That same server may also wish to