(RADIATOR) Multi chassis Multilink PPP-Proposal for a new feature(add-on)

Hugh Irvine hugh at open.com.au
Sun Jan 5 21:10:24 CST 2003


Hello Marius -

I recently implemented exactly this scenario for a customer on a  
consulting job.

The solution we came up with was to use additional fields in the  
session database, and stored procedures in the database itself (Oracle)  
to do exactly what you describe. The Radiator configuration file simply  
used a simple AuthBy PLSQL clause (you will find it in  
"goodies/AuthPLSQL.pm" - thanks to Pavel Crasotin) and everything else  
was done by the stored procedure.

regards

Hugh


On Monday, Jan 6, 2003, at 05:37 Australia/Melbourne,  
MStefan at enertel.nl wrote:

>
>
>
> Description:
> One of the possible scenarios in one modem environment is to have  
> multiple
> LNSs for one client (this is required either for more capacity or from
> redundancy reasons).The challenge in this kind of environments is to
> terminate the second session of one ISDN user on the same LNS where the
> first session was terminated. Also to set the maximum number of  
> sessions per
> each LNS
>
> Usually the first item is solved by means of a protocol implemented  
> between
> the NAS and the LNS (SGBP for ex) ,in an environment that is working  
> without
> a Policy Manager. The drawback here is that this protocol needs a lot  
> of
> resources from the NAS&LNS not to mention that is not elegant
> The second item usually is taken care by a Policy Manager(including LNS
> detection etc)
>
>
> I can think of something like  inserting in the sessiondatabase also  
> the LNS
> IP or tunnel preference (when a user is accepted) and based on this the
> second channel should get the same items in the reply(overwriting the
> default reply) but probably there are more elegant ways to do this
>
> Is anyone doing this or are there some plans to implement something  
> like
> this in the Radiator as an optional.
> Thanks in advance
>
> Kind Regards
>
> Marius Stefan
> Service Designer/Development Department
> Enertel N.V
> K.P van der Mandelelaan 130-144
> 3062 MB Rotterdam
> Postbus 25226
> 3001 HE Rotterdam
> Phone:+31(0)10 880 3798
> Fax    :+31(0)10 880 3901
> Mobile:+31(0)65 460 4973
> www.enertel.nl
>
>
>
>
> #********************************************************************** 
> *****
> #
> # Dit e-mailbericht met eventuele attachments is uitsluitend bestemd  
> voor de
> # geadresseerde(n) en bevat mogelijk vertrouwelijke gegevens en/of is
> # beschermd door intellectuele eigendomsrechten. Bent u niet de
> # geadresseerde, neemt u dan zo spoedig mogelijk contact op met de  
> afzender
> # en verzoeken wij u het e-mailbericht en eventuele attachments van uw
> # computer te verwijderen. Elk gebruik van de inhoud van dit  
> e-mailbericht
> # en eventuele attachments (waaronder verveelvoudiging, verspreiding  
> of het
> # anderzins openbaar maken in welke vorm dan ook) door andere personen  
> dan
> # de bedoelde geadresseerden is verboden. De weergegeven mening is puur
> # persoonlijk en hoeft niet noodzakelijk over een te komen met die van
> # Enertel. Enertel is niet aansprakelijk voor de inhoud van dit
> # e-mailbericht en eventuele attachments.
>
>
> ===
> 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.
>
>

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
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.


More information about the radiator mailing list