(RADIATOR) Ascend-coldstart

[Hugh Irvine]

Hello Jerome -

It would be simplest if you could send us a copy of your patch and we 
will roll it into the base code.

thanks and regards

Hugh


On 10/01/2004, at 2:42 AM, Jerome Fleury wrote:

> Hi there,
>
> it seems like Radiator handles really badly the Ascend event 
> 'Coldstart'.
>
> let me explain this:
>
> The Ascend NAS is supposed to send this Event-Request at every reboot, 
> so that the server can
> cleanup the session table.
>
> the debug says:
>
> *** Received from 212.129.4.13 port 6974 ....
> Code:       Ascend-Access-Event-Request
> Identifier: 190
> Authentic:  <179><249><24><8><159><177><220>nF-<10><186><0><228>H<2>
> Attributes:
>         NAS-IP-Address = 212.129.4.13
>         Ascend-Event-Type = Ascend-ColdStart
>
> *** Sending to 212.129.4.13 port 6974 ....
> Code:       Ascend-Access-Event-Response
> Identifier: 190
> Authentic:  <179><249><24><8><159><177><220>nF-<10><186><0><228>H<2>
> Attributes:
>
> This could look OK, but the Ascend documentation says:
>
> Ascend-Event-Type (150)
>
> Description: Indicates one of the following:
>
> A cold-start notification, informing the accounting server that the 
> MAX TNT has started up
> A session event, informing the authentication server that a session 
> has begun
>
> Usage: For a cold-start notification, 
> Ascend-Event-Type=Ascend-Coldstart (1). For a session
> event, Ascend-Event-Type=Ascend-Session-Event (2).
>
> Dependencies: In a cold-start notification, the MAX TNT sends values 
> for NAS-Identifier,
> Ascend-Event-Type, and Ascend-Number-Sessions in an 
> Ascend-Access-Event-Request packet (code
> 33). The RADIUS accounting server must send back an 
> Ascend-Access-Event-Response packet (code
> 34) with the correct identifier to the MAX TNT.
>
>
> That means the radius server has to send a NAS-Identifier (or 
> something like, this is quite not
> clear) for the NAS to accept the response.
>
> On our config it looks like the NAS doesn't accept the response from 
> Radiator and keeps
> retransmitting the Event-Request.
>
> I think I'll have to code a patch (better than a hook indeed) so that 
> Radiator handles this
> correctly.
>
> What do you think about it ? Has someone here already face this 
> problem ?
>
> Tchuss.
> --
> Jerome Fleury
> ===
> 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.
>
>

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.



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.