[ previous ] [ next ] [ threads ]
 
 From:  "Steven McCoy" <fnjordy at gmail dot com>
 To:  "Alex M" <radiussupport at lrcommunications dot net>
 Cc:  "Mono Dev List" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Central Dynamic Configuration for Captive Portal RADIUS
 Date:  Wed, 29 Mar 2006 19:51:39 -0500
Whats wrong with using DNS for this?

--
Steve-o

On 29/03/06, Alex M <radiussupport at lrcommunications dot net> wrote:
>
> Hi, I'm trying to create a system where I will be able to mange hotspots
> more dynamically and from central location. I want to begin by creating
> "algorithm" where the list of Radius servers for captive portal could be
> obtained automatically from the central WEB server or secondary backup
> server.
>
>
>
> The reason for this is faster and easy management, quality of service
> configuration and scalability. Here is how it works: At startup NAS (M0n0)
> connects to preset DNS URL and read config file that has a list of Radius
> servers (and maybe other configuration) [also beside this dynamic function
> nas should have static info on 2 radius servers, just in case, but those 2
> will be added et the end of the list, if connection is ok] so about the
> list. the list obtained from server will contain all available Radiuses,
> now
> when the list is obtained nas will ping all nases and once with the low
> pings will be placed in the beginning of the list. .
>
>
>
> Also, there should be implementations of groups so that we can assign
> nases
> to proper Radiuses and change the groups during maintenance.
>
>
>
> Do I make myself clear on what I want?  Do you want to implement my Idea?
>
> Does any one want to work with me on this?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Regards,
>
> Oleksandr
>
> LRC
>
>
>
>
>