RE: [MeshBox-radius] RE: MeshBox-radius digest, Vol 1 #8 - 1 msg

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi Ray,

I have been talking to Mark on this - I think it makes sense to truly
distribute the database (ie not mirror). This can be done quite easily
with realms in Radius; but I am not sure that this is necessarily the
way forward.

Initial thoughts: I think it makes sense to consider an LDAP backend
which can later be used to provide other services to users like email,
web, etc; and also allow preferences to be centrally stored for people
wanting to roam. I haven't spent a lot of time on this yet - but the key
must be speed, scalability and data reusability. I am also an advocate
of non-centralised database, I don't like the idea of one group
controlling everything.

Regards

Eden

> -----Original Message-----
> From: mes...@li... 
> [mailto:mes...@li...] On Behalf 
> Of shaitan
> Sent: 03 March 2003 00:45
> To: mes...@li...
> Subject: [MeshBox-radius] RE: MeshBox-radius digest, Vol 1 #8 - 1 msg
> 
> 
> Hi Guys,
> 
> I know my way around mysql and am vaguely familiar with 
> radius packages.
> I have came across the following docco which should do what we need
> regarding using a db for the authentication info.
> 
> http://www.frontios.com/freeradius.html
> 
> To answer your questions mark, its not the amount of records that is
> going to be the issue as such, but more the delay in authenticating
> users across the net, so would I would suggest is that every mesh node
> have a local copy of the data for their region. Maybe split the users
> into geographical groups, and if you server resides in the 
> coverage area
> for this group, then it will cache this data.
> 
> What do you reckon?
> 
> Cheers
> 
> Ray
> 
> > -----Original Message-----
> > From: mes...@li... 
> > [mailto:mes...@li...] On Behalf 
> > Of mes...@li...
> > Sent: 02 March 2003 21:22
> > To: mes...@li...
> > Subject: MeshBox-radius digest, Vol 1 #8 - 1 msg
> > 
> > 
> > Send MeshBox-radius mailing list submissions to
> > 	mes...@li...
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	https://lists.sourceforge.net/lists/listinfo/meshbox-radius
> > or, via email, send a message with subject or body 'help' to
> > 	mes...@li...
> > 
> > You can reach the person managing the list at
> > 	mes...@li...
> > 
> > When replying, please edit your Subject line so it is more 
> > specific than "Re: Contents of MeshBox-radius digest..."
> > 
> > 
> > Today's Topics:
> > 
> >    1. RE: Distributed Radius Project (Mark Malewski)
> > 
> > --__--__--
> > 
> > Message: 1
> > From: "Mark Malewski" <mar...@ne...>
> > To: <ede...@lt...>,
> > 	<mes...@li...>,
> > 	<e...@ne...>
> > Subject: RE: [MeshBox-radius] Distributed Radius Project
> > Date: Sat, 1 Mar 2003 18:43:58 -0600
> > 
> > Oh, now you want us to architect this huh?  Why do you think 
> > we've been screaming for help?
> > 
> > Ok, there are a few people on the list that understand how to 
> > make it secure, but no one really knows how we're going to do 
> > the databases, or get them to work.  So that's why we needed 
> > some DB guys to figure all this stuff out.  
> > 
> > Imagine that we're trying to create a very large database 
> > (similar to what NodeDB is doing for all their nodes).  
> > Except it will store the authentication information for each 
> > user (their login/password as well as a lat/long, etc.)
> > 
> > This will allow users to roam freely between wireless 
> > communities, and go from community to community, or state to 
> > state, or country to country with one login, and one password.
> > 
> > Now how can we do this?  Initially, we'd like to create one 
> > database, and have it mirrored to a backup server (for 
> > redundancy).  <Looking around the room for help>
> > 
> > We'd like to be able to manage it from the current website 
> > (using a web-based control panel that we currently have in 
> > place).  This allows us to assign certain users "admin 
> > privilages" and they can add/delete/edit users.  It also 
> > allows us to assign "classes" of users (different levels of 
> > bandwidth throttling).  We'd also like it to convert the 
> > user's address to a lat/long coordinate, and store it into 
> > the database (as a lat/long).  Then as they roam around, 
> > their lat/long is updated (based on triangulation), and 
> > automatically remapped on the MapServer.
> > 
> > Let's say for now, about 5,000 users.  Is that feasible?  
> > Maybe a year from now, about 15,000 users.
> > 
> >        Mark
> > 
> > 
> > -----Original Message-----
> > From: mes...@li...
> > [mailto:mes...@li...] On Behalf 
> > Of Eden Akhavi
> > Sent: Saturday, March 01, 2003 3:07 PM
> > To: mes...@li...
> > Subject: [MeshBox-radius] Distributed Radius Project
> > 
> > 
> > Hi,
> > 
> > I am trying to find out what the plans are here - I have seen 
> > the subtasks in the SF Task manager, but I am not clear on 
> > the architecture. Has anyone architected this.
> > 
> > Also what is the scope of this project, how many users is the 
> > auth database looking to scale to?
> > 
> > Regards
> > 
> > 
> > 
> > 
> > Eden
> > 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf 
> > _______________________________________________
> > MeshBox-radius mailing list Mes...@li...
> > https://lists.sourceforge.net/lists/listinfo/meshbox-radius
> > 
> > 
> > 
> > 
> > --__--__--
> > 
> > _______________________________________________
> > MeshBox-radius mailing list Mes...@li...
> > https://lists.sourceforge.net/lists/listinfo/meshbox-radius
> > 
> > 
> > End of MeshBox-radius Digest
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> MeshBox-radius mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/meshbox-radius
> 