[ previous ] [ next ] [ threads ]
 
 From:  "Alex M" <radiussupport at lrcommunications dot net>
 To:  "'Steven McCoy'" <fnjordy at gmail dot com>
 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 20:02:59 -0500
a) DNS is not yes supported
b) Current config supports only 2 servers
c) DNS are good but you are limited only to controlling where would and IP,
you can not add configuration such as groups for different locatios and
group switching id the server is not responding, basically with DNS all the
work will be manually. And in case of my idea it will be automatically self
existing. If you even can add command on radius servers to automatically
populate config file when the servr is up, and if server is not responding,
delete it from the list and notify admins



 

-----Original Message-----
From: Steven McCoy [mailto:fnjordy at gmail dot com] 
Sent: Wednesday, March 29, 2006 7:52 PM
To: Alex M
Cc: Mono Dev List
Subject: Re: [m0n0wall-dev] Central Dynamic Configuration for Captive Portal
RADIUS

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