(RADIATOR) Disconnect and Change-of-Authorization Messages

[Hugh Irvine]

Hello Jose -

All I can suggest is that you read the Radiator source code and do some 
experiments.

regards

Hugh


On 31 Mar 2004, at 02:30, José Borges Ferreira wrote:

>
> Like i told before , we already have several agreements with roamers 
> and have exchanged IP/Secrets for Radius.
>
>
> -----------
> | Roamer A  | -----\    ----------
> -----------        \  | Radiator |
> -----------        /   ----------
> | Roamer B  | -----/   | Custom   |
> -----------           | Module   |
>                        ----------
>             --- HTTP ---|  |  |---- SNMP -|
>             |              |              |
>             |              |Radius        |
>         ---------    ---------     ---------
>        |  NAS 1  |  |  NAS 2  |   |  NAS 3  |
>         ---------    ---------     ---------
>
>
> On the NASes i can have user belonging (authenticated) by Roamer A or 
> B.
>
> By using Radiator i want to :
>
> - Use the current Radius auth/acct settings for all of them.
> - Doesn't have to concern with a IP/UDP/Radius stack. You allready 
> have a great work done here ;)
> - Control witch user each Client (Roamer) can disconnect/change witch 
> user.
> - Since user can have more than one access method , i must support all 
> the diffrents NASes.
>
>
>
> Hugh Irvine wrote:
>
>>
>> Hello Jose -
>>
>> If you are using radius, then it is probably easiest to just use the 
>> radius Disconnect-Request (assuming that your NAS supports it).
>>
>> You should check with your NAS vendor.
>>
>> Otherwise I am not convinced that using Radiator is the correct 
>> approach.
>>
>> regards
>>
>> Hugh
>>
>>
>> On 29 Mar 2004, at 22:23, José Borges Ferreira wrote:
>>
>>> I want to provide to roamers  partners a disconnect facillity. The 
>>> use of Radius is obvious , since we allready have secure and 
>>> authorized traffic exchange established.
>>>
>>> I would like to develop ( actually extend ) a custom AuthBy Module 
>>> to allow the partner to disconnect "their" user. The module should 
>>> also understand the NAS type of the user and use the correct method 
>>> for that NAS ( SNMP, HTTP or RADIUS).
>>>
>>> My doubts are :
>>>    This should be treated the same way as Authentication requests or 
>>> Accounting requests.
>>>    If  so , should i be process them on handle_request or any other 
>>> method.
>>>
>>> <j/>
>>
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.