meshbox-radius — MeshBox Authentication Server Development

[MeshBox-radius] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

[MeshBox-radius] RE: NoCatAuth experience?

[shaitan <sh...@cl...>]

Ah, fair enough

> -----Original Message-----
> From: Mark Malewski [mailto:mar...@ne...] 
> Sent: 08 March 2003 14:44
> To: 'shaitan'; mes...@li...; 
> ede...@lt...; e...@ne...; mol...@ho...
> Subject: RE: NoCatAuth experience?
> 
> 
> > >i actually did more with the radius stuff (like added basic,
> > rudimentary
> > >accounting).  but that was after i was authenticating.
> 
> NoCat doesn't fully support this.  These are 
> changes/improvements that Rodney made to his version of 
> NoCat.  Understand that RADIUS can do a lot of things (but 
> they haven't all been implemented in NoCat).
> 
>           Mark
> 
> -----Original Message-----
> From: shaitan [mailto:sh...@cl...] 
> Sent: Saturday, March 08, 2003 8:38 AM
> To: 'Mark Malewski'; ede...@lt...; 
> e...@ne...; reb...@ab...; 
> mol...@ho...; mes...@li...
> Subject: RE: NoCatAuth experience?
> 
> Hi Mark,
> 
> I thought by default radius did logging anyway? Or is he 
> talking about logging in addition to the normal login/logout entries?
> 
> Ray
> 
> > -----Original Message-----
> > From: Mark Malewski [mailto:mar...@ne...]
> > Sent: 07 March 2003 22:17
> > To: sh...@cl...; ede...@lt...; 
> > e...@ne...; reb...@ab...; 
> > mol...@ho...; mes...@li...
> > Subject: RE: NoCatAuth experience?
> > 
> > 
> > Ray/Eden/E/Jason/Rodney,
> > 
> > >i actually did more with the radius stuff (like added basic,
> > rudimentary
> > >accounting).  but that was after i was authenticating.
> > 
> > Would this be of any use to us?  I'd like to add the
> > accounting functionality to NoCat, could we get it to work 
> > with LDAP (later in the future)?  What are your thoughts?  
> Ray?  Eden?
> > 
> >        Mark
> > 
> 

[MeshBox-radius] RE: NoCatAuth experience?

[Mark M. <mar...@ne...>]

> >i actually did more with the radius stuff (like added basic,
> rudimentary
> >accounting).  but that was after i was authenticating.

NoCat doesn't fully support this.  These are changes/improvements that
Rodney made to his version of NoCat.  Understand that RADIUS can do a
lot of things (but they haven't all been implemented in NoCat).

          Mark

-----Original Message-----
From: shaitan [mailto:sh...@cl...] 
Sent: Saturday, March 08, 2003 8:38 AM
To: 'Mark Malewski'; ede...@lt...; e...@ne...;
reb...@ab...; mol...@ho...;
mes...@li...
Subject: RE: NoCatAuth experience?

Hi Mark,

I thought by default radius did logging anyway? Or is he talking about
logging in addition to the normal login/logout entries?

Ray

> -----Original Message-----
> From: Mark Malewski [mailto:mar...@ne...] 
> Sent: 07 March 2003 22:17
> To: sh...@cl...; ede...@lt...; 
> e...@ne...; reb...@ab...; 
> mol...@ho...; mes...@li...
> Subject: RE: NoCatAuth experience?
> 
> 
> Ray/Eden/E/Jason/Rodney,
> 
> >i actually did more with the radius stuff (like added basic,
> rudimentary
> >accounting).  but that was after i was authenticating.
> 
> Would this be of any use to us?  I'd like to add the 
> accounting functionality to NoCat, could we get it to work 
> with LDAP (later in the future)?  What are your thoughts?  Ray?  Eden?
> 
>        Mark
> 

[MeshBox-radius] RE: NoCatAuth experience?

[shaitan <sh...@cl...>]

Hi Mark,

I thought by default radius did logging anyway? Or is he talking about
logging in addition to the normal login/logout entries?

Ray

> -----Original Message-----
> From: Mark Malewski [mailto:mar...@ne...] 
> Sent: 07 March 2003 22:17
> To: sh...@cl...; ede...@lt...; 
> e...@ne...; reb...@ab...; 
> mol...@ho...; mes...@li...
> Subject: RE: NoCatAuth experience?
> 
> 
> Ray/Eden/E/Jason/Rodney,
> 
> >i actually did more with the radius stuff (like added basic,
> rudimentary
> >accounting).  but that was after i was authenticating.
> 
> Would this be of any use to us?  I'd like to add the 
> accounting functionality to NoCat, could we get it to work 
> with LDAP (later in the future)?  What are your thoughts?  Ray?  Eden?
> 
>        Mark
> 

[MeshBox-radius] RE: NoCatAuth experience?

[J M <mol...@ho...>]

I tried the March 6th nightly build, and it was having the same problem, and 
producing the same log messages as described in previous posts to the nocat 
mail list. Most posts point back to permissions on the pgp directory, but 
I've tried many combo's with same results.

Jason

Permissions on .../pgp/ on gateway

-rw-r--r--    1 www-data www-data        0 Mar  6 16:01 pubring.gpg
-rw-r--r--    1 www-data www-data        0 Mar  6 16:01 secring.gpg
-rw-------    1 www-data www-data     1978 Mar  7 15:43 trustedkeys.gpg

nocat.log output. where 192.168.3.100 is client wireless, and 10.3.1.1 is 
backbone ip of AP.

Connection to 10.3.1.1 from 192.168.3.100
[2003-03-07 16:03:15] Capturing  192.168.3.100  for http://www.news.com/
[2003-03-07 16:03:15] Notifying parent of Capture on peer 192.168.3.100
[2003-03-07 16:03:15] Got notification Capture of peer 192.168.3.100
[2003-03-07 16:03:15] Child process returned 1
[2003-03-07 16:03:41] Spawning child process 2703.
[2003-03-07 16:03:41] Connection to 10.3.1.1 from 192.168.3.100
[2003-03-07 16:03:41] Received notify from 192.168.3.100
[2003-03-07 16:03:41] gpg --decrypt --homedir=/usr/local/nocat/bin/../pgp 
--keyring trustedkeys.gpg --no-tty -o- returned error message:
gpg: Signature made Fri Mar  7 16:08:48 2003 EST using RSA key ID 3CC64F86
gpg: [don't know]: invalid packet (ctb=00)
gpg: read_keyblock: read error: invalid packet
gpg: enum_keyblocks failed: invalid keyring
gpg: Can't check signature: public key not found
[2003-03-07 16:03:41] gpg --decrypt --homedir=/usr/local/nocat/bin/../pgp 
--keyring trustedkeys.gpg --no-tty -o- returned error: Illegal seek ( 2 )
[2003-03-07 16:03:41] Invalid notify from 192.168.3.100
[2003-03-07 16:03:41] Capturing  192.168.3.100  for 
http://10.3.1.1:5280/?ticket=o .......


Jason





>From: "Mark Malewski" <mar...@ne...>
>To: "'Rodney Ebersole'" 
><reb...@ab...>,<mes...@li...>,<mol...@ho...>,"'Bob 
>Larkin'" 
><bob...@ho...>,<ede...@lt...>,<sh...@cl...>
>Subject: RE: NoCatAuth experience?
>Date: Fri, 7 Mar 2003 16:02:45 -0600
>
>Rodney,
>
>Thanks for the help, I'll have Jason, and a few of the others get in
>contact with you if they have any other questions.
>
>          Mark
>
>-----Original Message-----
>From: Rodney Ebersole [mailto:reb...@ab...]
>Sent: Friday, March 07, 2003 3:45 PM
>To: Mark Malewski
>Subject: RE: NoCatAuth experience?
>
>Mark,
>
>which nightly build?  i have the march 1, 2003 build working
>with radius.  i did make some mods, however.  the main thing
>was that i removed the dynamic host-checking from authenticate_user().
>i also changed radius() so that servers with accounting ports (1646,
>1813)
>do not get used for authenticating.
>
>i actually did more with the radius stuff (like added basic, rudimentary
>accounting).  but that was after i was authenticating.
>
>Mark Malewski wrote:
>
> > Schuyler,
> >
> > I've checked the NoCatAuth list as well.  Maybe you could shed some
> > light on this problem?  Has this been fixed in the latest distro?  Any
> > ideas on how to fix it?
> >
> >             Mark
> >
> > -----Original Message-----
> > From: mes...@li...
> > [mailto:mes...@li...] On Behalf Of J
>M
> > Sent: Friday, March 07, 2003 2:23 PM
> > To: mes...@li...
> > Subject: [MeshBox-Dev] NoCatAuth experience?
> >
> > Anyone have NocatAuth (nightly build) working? I'm working on the
>final
> > piece of the Debian install, but NocatAuth repeatedly returns to the
> > login
> > screen afetr succeccful radius authentication. It is discussed on the
> > NocatAuth maillist, but doesn't appear to be answered anywhere.
> >
> > Thanks
> >
> > Jason
> >


_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail

[MeshBox-radius] RE: NoCatAuth experience?

[Mark M. <mar...@ne...>]

Ray/Eden/E/Jason/Rodney,

>i actually did more with the radius stuff (like added basic,
rudimentary
>accounting).  but that was after i was authenticating.

Would this be of any use to us?  I'd like to add the accounting
functionality to NoCat, could we get it to work with LDAP (later in the
future)?  What are your thoughts?  Ray?  Eden?

       Mark

[MeshBox-radius] RE: NoCatAuth experience?

[Mark M. <mar...@ne...>]

Rodney,

Thanks for the help, I'll have Jason, and a few of the others get in
contact with you if they have any other questions.

         Mark

-----Original Message-----
From: Rodney Ebersole [mailto:reb...@ab...] 
Sent: Friday, March 07, 2003 3:45 PM
To: Mark Malewski
Subject: RE: NoCatAuth experience?

Mark,

which nightly build?  i have the march 1, 2003 build working
with radius.  i did make some mods, however.  the main thing
was that i removed the dynamic host-checking from authenticate_user().
i also changed radius() so that servers with accounting ports (1646,
1813)
do not get used for authenticating.

i actually did more with the radius stuff (like added basic, rudimentary
accounting).  but that was after i was authenticating.

Mark Malewski wrote:

> Schuyler,
>
> I've checked the NoCatAuth list as well.  Maybe you could shed some
> light on this problem?  Has this been fixed in the latest distro?  Any
> ideas on how to fix it?
>
>             Mark
>
> -----Original Message-----
> From: mes...@li...
> [mailto:mes...@li...] On Behalf Of J
M
> Sent: Friday, March 07, 2003 2:23 PM
> To: mes...@li...
> Subject: [MeshBox-Dev] NoCatAuth experience?
>
> Anyone have NocatAuth (nightly build) working? I'm working on the
final
> piece of the Debian install, but NocatAuth repeatedly returns to the
> login
> screen afetr succeccful radius authentication. It is discussed on the
> NocatAuth maillist, but doesn't appear to be answered anywhere.
>
> Thanks
>
> Jason
>
> _________________________________________________________________
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The
> debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost
> and
> disoriented. TotalView can help you find your way. Available on major
> UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Meshbox-developers mailing list
> Mes...@li...
> https://lists.sourceforge.net/lists/listinfo/meshbox-developers
>
> _______________________________________________
> NoCat mailing list
> No...@li...
> http://lists.nocat.net/mailman/listinfo/nocat

[MeshBox-radius] RE: I am developing a new routing algorithm

[Mario G. <mgi...@li...>]

Il sab, 2003-02-22 alle 09:14, Mark Malewski ha scritto:
> Mario,
> 
> We're currently working on a similar project, would you like to give us
> a hand?  We could always use the help!  We could always use another
> developer, especially if you're experienced with IPv6, etc.
> 
> Send me a quick E-mail with your skills/qualifications/experience.
> 

> 
> -----Original Message-----
> From: Mario Giammarco [mailto:mgi...@li...] 
> Sent: Friday, February 21, 2003 6:36 AM
> To: mar...@ne...
> Subject: I am developing a new routing algorithm
> 
> Hello,
> I am developing a wireless routing algorithm as part of my master thesis
> in computer science.


I have put a wiki page in: mariosoft.swiki.net
-- 
Mario Giammarco <mgi...@li...>

[MeshBox-radius] Distributed Radius Project

[Mark M. <mar...@ne...>]

Well we need to store a current lat/long in each user's account for the
MeshNodeMapper anyways.  So that's not a problem.  We could use
triangulation software to update the lat/long (off of other nodes or IP
ping triangulation).

I'll look into this NeroGrid stuff, sounds interesting...

>One afterthought, whatever system we do will likely need some sort of 
>regional suffix/prefix to ensure that all usernames are globally
unique. I 

Yes, possibly use a two digit country code identifier (.us, .uk, etc.)

>can foresee that the most costly operation in this system will be
changing >a user's password ;)

Nah, I already have a web-based front end setup, with a nice PHP admin
control panel, so we'll have web-based administration, and also users
will be able to update their account information (and change/reset their
passwords) online.

>Just a thought.  BTW, anyone get a chance to look at the benchmarks of
the >new MySQL? I heard it was pretty speedy for simply queries.

Nope, but I heard the same.  I'm anxiously awaiting more info on it.
Have you tinkered with it at all?  I've been hearing lots of good things
about it, but haven't seen/used it yet.

          Mark

-----Original Message-----
From: mes...@li...
[mailto:mes...@li...] On Behalf Of Rick
Sent: Tuesday, March 04, 2003 3:36 AM
To: mes...@li...
Subject: Re: [MeshBox-radius] RE: MeshBox-radius digest, Vol 1 #8 - 1
msg


Aye,  I am a big fan of decentralized database for reasons of
redundancy, speed, and the piece of mind that there is no overlord (no
matter how benevolent). We would probably want to have the MeshAP seek
who it last authenticated from, since its likely it won't change, but if
the requested authentication server cannot authenticate that user, it
may do a neurogrid (decentralized search, see http://www.neurogrid.net )
style search. Since our data scope is slightly more constrained ;) we
could set up an abbreviated version of this and make it quite snappy.

One thought would be this: 
Set up the assignment of each authenticator in the global network to
include a latitude and longitude, storing the relationships to each of
its neighbor nodes in relation to direction. So when a user (Bob) flies
from Seattle to Chicago and tries to jump on the mesh at the airport,
the authenticating node simply says something to the effect of, "I don't
know this Bob fellow, but its coordinates are west of me". It then makes
a request of an authentication node sitting west of it. So it calls its
friend that's sitting outside a coffee shop in Dickenson which responds
the same, and so on, until a node that contains the proper user hash has
been found. This would require that some form of the users geographic
information be stored with their account number, like BJohnson47-122, or
perhaps some clever representation of the two+ numbers. Once the proper
credentials have been passed back to airport mesh in Chicago, it can
choose to store those for some time in its DB. 

The next time a request is made for said Bob (this time he finds himself
over in Cincinnati) the trail of authentication may find itself
intersecting with the trail from Chicago to Seattle. At which point any
one of the authentication boxes could say, "Those credentials just
passed through here, here they are." or at the very least, "MeshAP in
Chicago Airport was just looking for that guy, ask him." 

Just a thought.  BTW, anyone get a chance to look at the benchmarks of
the new MySQL? I heard it was pretty speedy for simply queries.

One afterthought, whatever system we do will likely need some sort of
regional suffix/prefix to ensure that all usernames are globally unique.
I can foresee that the most costly operation in this system will be
changing a user's password ;)

Thanks,
Rick

On Sun, 2003-03-02 at 15:45, shaitan wrote:
> 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




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The
debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost
and 
disoriented. TotalView can help you find your way. Available on major
UNIX 
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
MeshBox-radius mailing list
Mes...@li...
https://lists.sourceforge.net/lists/listinfo/meshbox-radius

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

[Rick <r.l...@ve...>]

Aye,  I am a big fan of decentralized database for reasons of
redundancy, speed, and the piece of mind that there is no overlord (no
matter how benevolent). We would probably want to have the MeshAP seek
who it last authenticated from, since its likely it won't change, but if
the requested authentication server cannot authenticate that user, it
may do a neurogrid (decentralized search, see http://www.neurogrid.net )
style search. Since our data scope is slightly more constrained ;) we
could set up an abbreviated version of this and make it quite snappy.

One thought would be this: 
Set up the assignment of each authenticator in the global network to
include a latitude and longitude, storing the relationships to each of
its neighbor nodes in relation to direction. So when a user (Bob) flies
from Seattle to Chicago and tries to jump on the mesh at the airport,
the authenticating node simply says something to the effect of, "I don't
know this Bob fellow, but its coordinates are west of me".
It then makes a request of an authentication node sitting west of it. So
it calls its friend that's sitting outside a coffee shop in Dickenson
which responds the same, and so on, until a node that contains the
proper user hash has been found. This would require that some form of
the users geographic information be stored with their account number,
like BJohnson47-122, or perhaps some clever representation of the two+
numbers. Once the proper credentials have been passed back to airport
mesh in Chicago, it can choose to store those for some time in its DB. 

The next time a request is made for said Bob (this time he finds himself
over in Cincinnati) the trail of authentication may find itself
intersecting with the trail from Chicago to Seattle. At which point any
one of the authentication boxes could say, "Those credentials just
passed through here, here they are." or at the very least, "MeshAP in
Chicago Airport was just looking for that guy, ask him." 

Just a thought.  BTW, anyone get a chance to look at the benchmarks of
the new MySQL? I heard it was pretty speedy for simply queries.

One afterthought, whatever system we do will likely need some sort of
regional suffix/prefix to ensure that all usernames are globally unique.
I can foresee that the most costly operation in this system will be
changing a user's password ;)

Thanks,
Rick

On Sun, 2003-03-02 at 15:45, shaitan wrote:
> 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

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

[Eden A. <ede...@lt...>]

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
> 

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

[shaitan <sh...@cl...>]

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
> 

RE: [MeshBox-radius] Distributed Radius Project

[Mark M. <mar...@ne...>]

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] Distributed Radius Project

[Eden A. <ede...@lt...>]

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

[MeshBox-radius] RE: Need help with creating a database / RADIUS Server

[Mark M. <mar...@ne...>]

Eden/Matt/Chris/Michael/Bob,
 
 
If you haven't done so already, please subscribe to this mailing list:
 
http://lists.sourceforge.net/lists/listinfo/meshbox-radius
 
Also please E-mail me your current sourceforge screen name/login, so I
can add you to the source forge developer's site.
 
 
We're trying to create a Global authentication server database.  
 
This is a BIG task.
 
These are the goals:
 
We're trying to create a global authentication server.  So users have
one login, and one password, and they can roam freely between wireless
MeshBox communities.  We'd like the User database to be manageable using
our current web-based control panel (php-based).  That way we can assign
permissions to certain users, and they can add/edit/manage user accounts
in their local area.
 
1) We currently have a user database
2) We'd like to use FreeRADIUS (for user authentication), and somehow
tie this to our current user database.
3) We'd like to use NoCat (for wireless authentication)
4) We need to add a Lat/Long field to the current database (need some
type of lat/long conversion program to convert an address to lat/long).
The mapping server will use this lat/long field for the Mapping of
MeshBox nodes.
5) We need to add address (and country code) information to the current
user database (and somehow convert the street address to a lat/long).
6) We need to update the web-based control panel pages with the
additional fields (address, country code, phone number, etc.) for easy
web-based administration.
 
Any ideas on how we can do all this?  Where shall we begin?  Do you want
to see what we currently have in place first?  <Looking around the room
for ideas>
 
         Mark
 
 

-----Original Message-----
From: Eden Akhavi [mailto:ede...@lt...] 
Sent: Friday, February 28, 2003 5:02 PM
To: 'Mark Malewski'
Subject: RE:  Need help with creating a database


Hi Mark,
 
What do you need?
 
Regards
 

Eden

-----Original Message-----
From: Mark Malewski [mailto:mar...@ne...] 
Sent: 28 February 2003 21:26
Subject: Need help with creating a database


Is anyone on this list a DBA person?  Someone that knows quite a bit
about databases, and how to create them, etc.
 
Looking for a little help, please contact me off-list.
 
             Thanks,
 
               Mark

[MeshBox-radius] RE: Too many hits to wiana.org ?

[Mark M. <mar...@ne...>]

Yes, this is something we're currently discussing and working on (and we
hope that Jon will join us).  

A new Global authentication server(s) that will perform the local
authentication for the community, and mirror WIANA.  

A "MeshServer" if you will.  New MeshServers will be brought online and
added to the network, as current servers become congested.

We're currently working out ideas on a "demo" box.  Once we get
everything up and running (and secure), we'll work with Jon and others
in the community on hosting "mirrors" of the authentication server.

The servers will communicate with one another, and share/update local
databases.

We're also working on some ping triangulation software (for the
MeshAP/MeshBox distro), that will ping each of the global authentication
servers, and the one with the quickest response (being closest/least
congested) will become the auth server for that MeshBox.

If you wish to participate/help with the Auth Server effort, please send
me an E-mail (with your skills, experience, qualifications) and we can
add you to the developer's list.  (Send me your source forge screen
name).

You can join the Global Auth/RADIUS Server mailing list here:

http://lists.sourceforge.net/lists/listinfo/meshbox-radius

         Thanks,

          Mark

P.S. Jon, if you could message me off-list, I would appreciate it.  I'd
like to make sure that you're an active part of the list/discussion so
that we can make sure that the MeshServer is completely compatible with
WIANA.  We also have lots of questions concerning WIANA.  We just want
to make sure that everything is compatible with the current WIANA system
(and the MeshServer package would be a simple "upgrade/install").



-----Original Message-----
From: Rick Richardson [mailto:rri...@et...] 
Sent: Wednesday, February 26, 2003 3:38 PM
To: me...@li...
Subject: RE: [MeshAP] Too many hits to wiana.org ?


Aye, mayhaps something like NTP server structure (but better). 
Where Wiana is the central authority, and there is a tier of computers
that sync with wiana, and another tier of computers that sync with
those. 

Gnutella is an example of a highly disorganized and rather inefficient
network, but accuracy and redundancy is not an issue with file sharing
in most cases.

Given that it could get nasty if there is a mistake, we might want to
build a p2p hierarchy controller that analyzes latency and specific
needs of geographic locations and builds the hierarchy with some level
of intelligence. 
Projects like that are quite fun and could be done while sleeping by
many of the folks on the [Decentralization] list :)



-----Original Message-----
From: Nate G [mailto:rfg...@ya...]
Sent: Tuesday, February 25, 2003 9:58 PM
To: me...@li...
Subject: [MeshAP] Too many hits to wiana.org ?


Every few minutes this thing tries to contact
wiana.org

If every node out there with a internet connection
hits your server this many times you are going to be
flooded in no time.

The Gnutella network solved the central server problem
a while back through a more distributed means, you may
want to look at that.


=====
Low cost meshnodes via dot bomb hardware
http://meshnet.sf.net

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

[MeshBox-radius] Re: [MeshAP] Our Mission Statement (Revision 1)

[Tom K. <to...@ka...>]

Dear Lee Hughes (what a gr8 wireless name that is)

You have what my old dad calls an "Old head on young shoulders" If your you=
nger than him....or me :-)

Stick around. This concept is valid. The hardware that Jon has made works. =
The business models we can argue about till the cows come home. The rights =
issues have never been resolved properly. If you can contribute, then we wi=
ll all welcome your effort. Please don't become jaded. This sort of thing a=
lways happens at the begining and at the end/implementation of any great id=
ea.=20

My first *bad* Linux experience was falling out with Patrick Volkerding in =
1993. He was a cobal guy and I had stupidly asked him if he could help me t=
o get my ex-wifes email bounced to me. (Her univeristy had the old crappy s=
endmail patch. Well, I was naive and Pat was a Pro - What can I say, I was =
desperate (the bitch divorced me anyway) and he said no way. But: I was the=
 first person - ever - to install Slackware. And I wrote the all the triden=
t video drivers. Big Fucking Deal. Pat remains the pro and I will always be=
 the numpty, and that experience taught me two lifelong lessons. 1) Dont ro=
ck "your" boat. Its the only boat you have -  and  - 2) Other people are no=
t interested in what motivates you.=20

Kindest Regards
TomKat







On 25 Feb 2003 15:00:43 +0000
Lee Hughes <lee...@to...> wrote:

> Hello I'm Lee, and this my view.
>=20
> I'm new to this list, been on it about 2 weeks, thought I'd get involved
> with meshap@locust. Now, all this infighting remind me off the stuff I=20
> used to see on the Smoothwall Lists, arguments, pointing of fingers,
> general nasty stuff. Both Projects have merit, Jon's box is cool, but to
> pricey for my needs, and this whole thing wiana is a bit of a mystery,
> I'm not keen oncentral control for any kind of network, and it looks
> like wiana could be come very important (and very profitable) for those
> involved with it? Correct me if I'm wrong on that..., maybe I
> misunderstand wiana function?
>=20
> is wiana something to do with cryptographic keys, if so, does this means
> aodv has now been 'secured' with crytographics signatures? now if it has
> then that's a software 'featured' I'd pay for and license, because
> that's hard to do. :-))). At the moment I could subvert a aodv network
> without layer 2 encryption, just by sending bogus routing
> replies....surley not good for the community.
>=20
> I'm not quite sure of the open sourceness of Locust, I'm not really that
> interested, to tell you the truth, fact of the matter is that you can
> download it, ripp it apart and make your own. I'm interested in packet
> shifters really, meshbox does this and that and meshbox makes you tea
> and does all other clever things too..which is ace!! I just need
> wireless coverage, as much as I can, and at as little cost, linux and
> aodv seem to be the ideal solution here. I've never been a fan of settop
> boxes, I think there pretty dull devices all in all, they limit the user
> in what they can do... put it this way I'd rather buy a portable linux
> computer, than a set top box right now.
>=20
> I like the fact that a source forge projects been setup, the projects
> gets more visablity, and hopefully more talented people will join in,
> the whole locust approach seems to be, download the source, try and work
> it out for yourself, and then ask questions. There's no mechanism for me
> to add patches or enhancements if I wanted to, because Jon's far too
> busy, because he's running a business at the end of the day, and if I
> were him, would he let me, a nobody.. interfere with his business? his
> lively hood? his future....no way...but I wish him loads of luck with
> his venture!
>=20
> So, meshap is, cool but's it's not the only way, forks are good=B7..
>=20
> no just don't fall out about it.....I heard Richard from smoothwall got
> his car done over, because of some of his comments, wow...the power of
> open source in-fighting ;-)
>=20
> Cheers,
> Lee =20
> 'although open source is cool, don't ever forget the names of the
> shoulders your standing on'=20
>=20
>=20
>=20
> On Fri, 2003-02-21 at 19:18, Mark Malewski wrote:
> > I would like to cordially invite/welcome everyone to the MeshBox.org
> > Developer's mailing list.  Thank-you for joining us.
> >=20
> > Let me begin by making a few things clear:
> >=20
> > 1) Our goal is to bring and support the development of MeshAP software
> > on hardware devices other than Jon's MeshAP device. =20
> >=20
> > 2) Continue to develop (and work hand in hand with Jon) on adding
> > additional features (IP Telephony, etc.) to the MeshAP/MeshBox distro.
> >=20
> > 3) Create ONE standard Free Global Wireless Network, where all mesh
> > users can talk/exchange data anywhere in the world.
> >=20
> > 4) Create a distro that will work on ALL PC platforms (not just MeshAP
> > boxes).
> >=20
> > 5) Offer inexpensive (around $200) pre-built hardware solutions (that
> > people can buy at $15 above our cost) that will run the MeshAP/MeshBox
> > software (like XBOX, PlayStation 2, etc.) The $15 profit will go to
> > developer's (such as Jon) to help support their hard work.
> >=20
> > 6) We are a NOT-FOR-PROFIT organization, and our mission is to help
> > people (this includes newbies) get online.  We will need to create
> > documentation, and FAQ's as well as "support teams/forums" where newbies
> > can ask questions.
> >=20
> > 7) We'll need to create a HCL (hardware compatibility list) of known
> > hardware that is supported/works.  This list will be constantly updated,
> > as we increase our support for various devices.
> >=20
> > 8) We'll add support for additional features such as IP Telephony, QoS,
> > etc.
> >=20
> > 9) We're not a "competing" or "incompatible" organization, nor are we
> > trying to create "a separate standard", we're simply a group of
> > volunteer developers that will work hand in hand (with Jon) in
> > supporting the MeshAP software.
> >=20
> > 10) All documents/FAQ's created by the MeshBox organization, will be
> > freely distributed (and given to Jon so that MeshBox members, and MeshAP
> > customers will have good documentation for current software releases).
> >=20
> >=20
> > This list will probably change (and grow), as the organization
> > progresses.  Our goal is to create a distro that is compatible with the
> > current MeshAP software/hardware, but with the additional bells and
> > whistles, and support for a wide range of other hardware (other than the
> > "official MeshAP device")
> >=20
> >=20
> >=20
> > If you're looking for help on using MeshAP software on ANY device other
> > than Jon's official MeshAP hardware, then please join the MeshBox
> > newbies list for hardware & support questions:
> >=20
> > mes...@li...
> >=20
> > If you're a developer, and want to help develop the MeshAP software,
> > then please join the MeshBox developer's list:
> >=20
> > mes...@li...
> >=20
> >=20
> > If you'd like to join the effort to create a global authentication
> > server for the MeshNetwork, then please join or RADIUS developer's list:
> >=20
> > mes...@li...
> >=20
> >=20
> >=20
> >                 Thank-you,
> >=20
> >               Mark Malewski
> >=20
> > =20
> >=20
>=20
>=20

[MeshBox-radius] Re: [MeshAP] Our Mission Statement (Revision 1)

[Ben P. <be...@pi...>]

Lee,
Good to have some sense making a resurgance on this list. I couldn't have
said it better.
Particularly the 'names of the shoulders' quote at the end. It would be good
if both communities could develop a healthier relationship than the one
which seems to be developing at the moment. I am particularly interested in
this project and (when I finish my degree) am keen to get involved. There
currently seems like more opportunity for this to happen with the
sourceforge setup than the locustworld one, i'm sure others feel this way
also.
Anyway, just registering my view too.
Ben

PS, I wouldn't mind a bit more information on WIANA too

----- Original Message -----
From: "Lee Hughes" <lee...@to...>
To: "Mark Malewski" <mar...@ne...>
Cc: <mes...@li...>;
<mes...@li...>;
<mes...@li...>; <me...@li...>
Sent: Tuesday, February 25, 2003 3:00 PM
Subject: Re: [MeshAP] Our Mission Statement (Revision 1)


Hello I'm Lee, and this my view.

I'm new to this list, been on it about 2 weeks, thought I'd get involved
with meshap@locust. Now, all this infighting remind me off the stuff I
used to see on the Smoothwall Lists, arguments, pointing of fingers,
general nasty stuff. Both Projects have merit, Jon's box is cool, but to
pricey for my needs, and this whole thing wiana is a bit of a mystery,
I'm not keen oncentral control for any kind of network, and it looks
like wiana could be come very important (and very profitable) for those
involved with it? Correct me if I'm wrong on that..., maybe I
misunderstand wiana function?

is wiana something to do with cryptographic keys, if so, does this means
aodv has now been 'secured' with crytographics signatures? now if it has
then that's a software 'featured' I'd pay for and license, because
that's hard to do. :-))). At the moment I could subvert a aodv network
without layer 2 encryption, just by sending bogus routing
replies....surley not good for the community.

I'm not quite sure of the open sourceness of Locust, I'm not really that
interested, to tell you the truth, fact of the matter is that you can
download it, ripp it apart and make your own. I'm interested in packet
shifters really, meshbox does this and that and meshbox makes you tea
and does all other clever things too..which is ace!! I just need
wireless coverage, as much as I can, and at as little cost, linux and
aodv seem to be the ideal solution here. I've never been a fan of settop
boxes, I think there pretty dull devices all in all, they limit the user
in what they can do... put it this way I'd rather buy a portable linux
computer, than a set top box right now.

I like the fact that a source forge projects been setup, the projects
gets more visablity, and hopefully more talented people will join in,
the whole locust approach seems to be, download the source, try and work
it out for yourself, and then ask questions. There's no mechanism for me
to add patches or enhancements if I wanted to, because Jon's far too
busy, because he's running a business at the end of the day, and if I
were him, would he let me, a nobody.. interfere with his business? his
lively hood? his future....no way...but I wish him loads of luck with
his venture!

So, meshap is, cool but's it's not the only way, forks are good7..

no just don't fall out about it.....I heard Richard from smoothwall got
his car done over, because of some of his comments, wow...the power of
open source in-fighting ;-)

Cheers,
Lee
'although open source is cool, don't ever forget the names of the
shoulders your standing on'



On Fri, 2003-02-21 at 19:18, Mark Malewski wrote:
> I would like to cordially invite/welcome everyone to the MeshBox.org
> Developer's mailing list.  Thank-you for joining us.
>
> Let me begin by making a few things clear:
>
> 1) Our goal is to bring and support the development of MeshAP software
> on hardware devices other than Jon's MeshAP device.
>
> 2) Continue to develop (and work hand in hand with Jon) on adding
> additional features (IP Telephony, etc.) to the MeshAP/MeshBox distro.
>
> 3) Create ONE standard Free Global Wireless Network, where all mesh
> users can talk/exchange data anywhere in the world.
>
> 4) Create a distro that will work on ALL PC platforms (not just MeshAP
> boxes).
>
> 5) Offer inexpensive (around $200) pre-built hardware solutions (that
> people can buy at $15 above our cost) that will run the MeshAP/MeshBox
> software (like XBOX, PlayStation 2, etc.) The $15 profit will go to
> developer's (such as Jon) to help support their hard work.
>
> 6) We are a NOT-FOR-PROFIT organization, and our mission is to help
> people (this includes newbies) get online.  We will need to create
> documentation, and FAQ's as well as "support teams/forums" where newbies
> can ask questions.
>
> 7) We'll need to create a HCL (hardware compatibility list) of known
> hardware that is supported/works.  This list will be constantly updated,
> as we increase our support for various devices.
>
> 8) We'll add support for additional features such as IP Telephony, QoS,
> etc.
>
> 9) We're not a "competing" or "incompatible" organization, nor are we
> trying to create "a separate standard", we're simply a group of
> volunteer developers that will work hand in hand (with Jon) in
> supporting the MeshAP software.
>
> 10) All documents/FAQ's created by the MeshBox organization, will be
> freely distributed (and given to Jon so that MeshBox members, and MeshAP
> customers will have good documentation for current software releases).
>
>
> This list will probably change (and grow), as the organization
> progresses.  Our goal is to create a distro that is compatible with the
> current MeshAP software/hardware, but with the additional bells and
> whistles, and support for a wide range of other hardware (other than the
> "official MeshAP device")
>
>
>
> If you're looking for help on using MeshAP software on ANY device other
> than Jon's official MeshAP hardware, then please join the MeshBox
> newbies list for hardware & support questions:
>
> mes...@li...
>
> If you're a developer, and want to help develop the MeshAP software,
> then please join the MeshBox developer's list:
>
> mes...@li...
>
>
> If you'd like to join the effort to create a global authentication
> server for the MeshNetwork, then please join or RADIUS developer's list:
>
> mes...@li...
>
>
>
>                 Thank-you,
>
>               Mark Malewski
>
>
>

[MeshBox-radius] (no subject)

[Darwin P. <da...@10...>]

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

[MeshBox-radius] Re: [MeshAP] Our Mission Statement (Revision 1)

[Lee H. <lee...@to...>]

Hello I'm Lee, and this my view.

I'm new to this list, been on it about 2 weeks, thought I'd get involved
with meshap@locust. Now, all this infighting remind me off the stuff I=20
used to see on the Smoothwall Lists, arguments, pointing of fingers,
general nasty stuff. Both Projects have merit, Jon's box is cool, but to
pricey for my needs, and this whole thing wiana is a bit of a mystery,
I'm not keen oncentral control for any kind of network, and it looks
like wiana could be come very important (and very profitable) for those
involved with it? Correct me if I'm wrong on that..., maybe I
misunderstand wiana function?

is wiana something to do with cryptographic keys, if so, does this means
aodv has now been 'secured' with crytographics signatures? now if it has
then that's a software 'featured' I'd pay for and license, because
that's hard to do. :-))). At the moment I could subvert a aodv network
without layer 2 encryption, just by sending bogus routing
replies....surley not good for the community.

I'm not quite sure of the open sourceness of Locust, I'm not really that
interested, to tell you the truth, fact of the matter is that you can
download it, ripp it apart and make your own. I'm interested in packet
shifters really, meshbox does this and that and meshbox makes you tea
and does all other clever things too..which is ace!! I just need
wireless coverage, as much as I can, and at as little cost, linux and
aodv seem to be the ideal solution here. I've never been a fan of settop
boxes, I think there pretty dull devices all in all, they limit the user
in what they can do... put it this way I'd rather buy a portable linux
computer, than a set top box right now.

I like the fact that a source forge projects been setup, the projects
gets more visablity, and hopefully more talented people will join in,
the whole locust approach seems to be, download the source, try and work
it out for yourself, and then ask questions. There's no mechanism for me
to add patches or enhancements if I wanted to, because Jon's far too
busy, because he's running a business at the end of the day, and if I
were him, would he let me, a nobody.. interfere with his business? his
lively hood? his future....no way...but I wish him loads of luck with
his venture!

So, meshap is, cool but's it's not the only way, forks are good=B7..

no just don't fall out about it.....I heard Richard from smoothwall got
his car done over, because of some of his comments, wow...the power of
open source in-fighting ;-)

Cheers,
Lee =20
'although open source is cool, don't ever forget the names of the
shoulders your standing on'=20



On Fri, 2003-02-21 at 19:18, Mark Malewski wrote:
> I would like to cordially invite/welcome everyone to the MeshBox.org
> Developer's mailing list.  Thank-you for joining us.
>=20
> Let me begin by making a few things clear:
>=20
> 1) Our goal is to bring and support the development of MeshAP software
> on hardware devices other than Jon's MeshAP device. =20
>=20
> 2) Continue to develop (and work hand in hand with Jon) on adding
> additional features (IP Telephony, etc.) to the MeshAP/MeshBox distro.
>=20
> 3) Create ONE standard Free Global Wireless Network, where all mesh
> users can talk/exchange data anywhere in the world.
>=20
> 4) Create a distro that will work on ALL PC platforms (not just MeshAP
> boxes).
>=20
> 5) Offer inexpensive (around $200) pre-built hardware solutions (that
> people can buy at $15 above our cost) that will run the MeshAP/MeshBox
> software (like XBOX, PlayStation 2, etc.) The $15 profit will go to
> developer's (such as Jon) to help support their hard work.
>=20
> 6) We are a NOT-FOR-PROFIT organization, and our mission is to help
> people (this includes newbies) get online.  We will need to create
> documentation, and FAQ's as well as "support teams/forums" where newbies
> can ask questions.
>=20
> 7) We'll need to create a HCL (hardware compatibility list) of known
> hardware that is supported/works.  This list will be constantly updated,
> as we increase our support for various devices.
>=20
> 8) We'll add support for additional features such as IP Telephony, QoS,
> etc.
>=20
> 9) We're not a "competing" or "incompatible" organization, nor are we
> trying to create "a separate standard", we're simply a group of
> volunteer developers that will work hand in hand (with Jon) in
> supporting the MeshAP software.
>=20
> 10) All documents/FAQ's created by the MeshBox organization, will be
> freely distributed (and given to Jon so that MeshBox members, and MeshAP
> customers will have good documentation for current software releases).
>=20
>=20
> This list will probably change (and grow), as the organization
> progresses.  Our goal is to create a distro that is compatible with the
> current MeshAP software/hardware, but with the additional bells and
> whistles, and support for a wide range of other hardware (other than the
> "official MeshAP device")
>=20
>=20
>=20
> If you're looking for help on using MeshAP software on ANY device other
> than Jon's official MeshAP hardware, then please join the MeshBox
> newbies list for hardware & support questions:
>=20
> mes...@li...
>=20
> If you're a developer, and want to help develop the MeshAP software,
> then please join the MeshBox developer's list:
>=20
> mes...@li...
>=20
>=20
> If you'd like to join the effort to create a global authentication
> server for the MeshNetwork, then please join or RADIUS developer's list:
>=20
> mes...@li...
>=20
>=20
>=20
>                 Thank-you,
>=20
>               Mark Malewski
>=20
> =20
>=20

[MeshBox-radius] RE: Where are we headed? (Step 2: Updating Goals) Revision 6

[Mark M. <mar...@ne...>]

Andy,

Welcome to the group!  Here is an updated list of "Group Tasks".  Please
note that I put you on the RADIUS/Authentication server project.

          Thanks,

           Mark

----------------------------------------------------------------------

Ok, Here is the "latest revision".  I've added/revised the list a bit...
Here is Revision 6 (of many):

I believe some of our "long term" Task Group goals would be to:

1) Have a "community" instant messenger [Ben Pirt/Martin O'Shield?/Bob
Larkin/Efstratios Gavas]
2) Integrate some type of triangulation software so roaming users can
can see/track friends on their buddy list. (Yes, we'll need to setup
"privacy features" as well).  This triangulation software should/could
also be later used for 911/Emergency services, as well as to
"automatically plot" meshbox locations on a global Node map.  [Chris
Hart?/Rob Kyle/Bob Larkin/Efstratios Gavas]
3) IP Allocation - Implement IPv6? [Roger Weeks?/Chris Hart?/Rob Kyle]
4) Setup/Integrate IP Telephony [Ben Pirt/Martin O'Shield?]
5) Create an easy to use web-based GUI for QoS Packet Scheduling &
Traffic shaping (user bandwidth throttling), and adding/editing user
accounts. [Looking for volunteers]
6) Marketing/Group "Meshbox.org" branding [Reg Aldridge?]
7) Public Awareness [Bob Larkin-UK, Looking for volunteers]
8) Build a dynamic node mapping 'MeshAP' database (possibly work in
conjunction with NodeDB and Triangulation Task Group) [Bob Larkin,
Efstratios Gavas, Dominic Chambers] 
9) Setup "ping triangulation" software that will cause MeshAP boxes to
route traffic/authentication to the closest "local mirror"
(authentication server). [Efstratios Gavas, Bob Larkin, Jacques Caron]
10) Create a list/database of global "Installers" (volunteers that would
be willing to help local community members setup equipment, antenna's,
support, etc.  [Looking for volunteers, please E-mail me your name &
country/state/city]
11) Create distro's that are compatible with a wide range of hardware
platforms. [Mark Malewski, Bob Larkin, Dox?, Jason Mollman]
12) Create a HCL (Hardware Compatibility List) of known hardware that
works with the current distro.  [Joe]

I believe some of our "short term" (immediate) Task Group goals would be
to:

1) Integrate NoCatSplash w/ MeshAP.   [This task has been completed, and
has been implemented into the latest distro] 
2) Begin work on a FreeRADIUS authentication server [Jon/Mark
Malewski/Jacques Caron/Efstratios Gavas/Andy Walden]
3) Setup some Traffic/Bandwidth Shaping (based on user/member class)
[This task has been completed, and has been implemented into the NoCat
distro]
4) QoS Packet Scheduling, to support low-bandwidth audio/video streaming
& IP Telephony, and create a "standard" for broadcasting audio/video on
the mesh network [Lee Hughes, Paul Cummins, Looking for additional
volunteers]
5) IP Allocation - WIANA allocates addresses from the 1.x.x.x subnets to
MeshBoxes (and their clients) as the default (out-of-the-box) option.
[Jon?/Mark Malewski/Roger Weeks/Chris Hart/Rob Kyle/Efstratios Gavas]
6) Create a "MeshServer" with a distributable MySQL database.[Stuart
Henderson/Efstratios Gavas]
7) Create FAQ's, documentation, and User's Manuals [Dox, Reg Aldridge,
Kris Cote]
8) Create a focal point for the purchase of "cheap/bulk hardware orders"
and easy hardware distribution to the UK/EU/group.    [Mark Malewski, ]
9) Create a "The Incredible Bulk" website for posting bulk orders [John
Beverly, Ray Breen]
10) Financial (Group) Treasurer [Mark Malewski, Dox or Jason?]
11) Help raise funding/community support [Bob Larkin, ] 

The Source Forge site is up and running.  I'm slowly working on some
nice graphics and logos for the group.  

If you're a member of a Task Group (yes, even the docs guys!), please
E-mail me your source forge "login/screen name" so that I can add you to
the developer's/doc editor's list.

We always need Task Group leaders.  If anyone is interested in leading a
"task group", please let me know.  As it stands, if your name is listed
first, I put you down as the "lead" for that particular task group.
(Yes, at times... leading a Task Group can be compared to "herding
cats")

If there is a "question mark" next to your name, could you please drop
me a quick E-mail me confirming your willingness to support/work in
these key areas (Task Groups).  Also, if your name is not listed, and
you're willing 
to help out, please send me an E-mail letting me know which "task
groups" you'd be willing to support/join.

If there is anything that you would like to see added to the list (as a
goal of the group), then please contact me, and we can add it to the
list.  

You can put your name down (and step forward to be a "lead") at any
point in time, you just need 2 "follower/helpers" that agree to help
join you with the task.  This is to provide "oversight" and assurance to
the group that the task will in fact get done.

Once this list is posted, anyone can recommend anything, and the list
can be changed, but it will require "3 people" in order to create an
"additional task group".  This is a good number, so that we know that 3
people are responsible for that new task.  (So if one person decides "ah
forget about it" or gets "too busy" then no matter what, the task
should/will get done).

If you're interested (or have an idea) in starting a new Task Group,
please E-mail me... And we can work on finding some other people to help
with the goal/project.

             Mark

P.S. Please message me off-list, with your talents, and any areas that
you'd be willing to help out with.

[MeshBox-radius] RE: Radius stuff...

[Andy W. <an...@ti...>]

On Mon, 24 Feb 2003, Mark Malewski wrote:

> Andy/Bob/E,
>
> Bob & E, get Andy "up to speed" on what we're trying to do.  I have
> asked him to help us with the RADIUS server (and to work with E on
> this).

Can we start with a summarization of the goal and big picture?

> >Do you really want to write your own RADIUS server?
>
> Oh, of course not!  We're going to use FreeRadius.
>
> We're just putting some other stuff on there as well.  If you could help
> E get everything up and running, that would be great.
>
> Actually, let me put you in contact with "E" and Bob.  They'll be able
> to explain a bit, and get you up to speed on what we're doing.
>
> What I need your "expertise" is for the RADIUS server (the
> authentication server).  Maybe "coach" E along, and help him get
> everything up and running.  Then I'll explain the even bigger problem
> what we're working on.  ;-)

Okay, sure.

> Are you familiar with BIND at all?

Yes.


>      Mark
>
> P.S. Our authentication servers need this:
>
> 1) Linux
> 2) FreeRadius
> 3) MySQL (to store the user accounts)

These are well understood by me.

> 4) NoCat (to act as a Captive Portal/WI-FI authentication)

Hopefull this is well understood by others.

> Actually, let me give you a brief "synopsis" of how things work.
>
> 1) There will be an authentication server (FreeRADIUS)
> 2) There will be "meshboxes" which are set top boxes for surfing the
> internet, etc.  These boxes also act as wireless "Access Points" on the
> mesh network.

Is "set top" the best description, ie, on top of your TV set?

> 3) There will be "roaming clients" (PDA's, laptops, etc.) that will use
> the MeshBox's to connect to the internet.
>
>
> I believe we should use something like this:
>
> 1) Setup authentication server (RADIUS).
> 2) MeshBox's authenticate to Authentication Server via 802.1x.
> 3) User database is stored on authentication server. (along with
> login/passwords)
> 4) Roaming users, come in contact with a meshbox... the "captive portal"
> requests authentication from the wireless user.  The login/password is
> entered into the "splash page".  This request (from the wireless side)
> is sent via the Ethernet side to the authentication server.  If the
> authentication server verifies that the user login/password is correct
> then it allows the WI-FI user to connect/use the network (and surf the
> web, send mail, etc.)
>
> The problem I'm having (and looking to you for advice) is NOT the WIFI
> side, this is already done.  It's the "backbone" side between meshboxes
> and the authentication (FreeRADIUS) server(s).  What do you suggest that
> we use?  802.1x, correct?

802.1x is fine, though, I'm unsure of a free stable/mature server
implementation for Linux or BSD. I see open1x has moved slightly since the
last time I looked though.

> We need help setting it up (E, read the FreeRadius docs) and we need to
> make sure that the backbone (between meshbox & auth server) is as secure
> as humanly possible.  We need to make sure that the network couldn't
> "hi-jacked", or a rogue meshbox (or wireless user) couldn't sniff/steal
> passwords or join the network.

Not a problem.

andy

--
PGP Key Available at http://www.tigerteam.net/andy/pgp

[MeshBox-radius] RE: Radius stuff...

[Mark M. <mar...@ne...>]

Andy/Bob/E,

Bob & E, get Andy "up to speed" on what we're trying to do.  I have
asked him to help us with the RADIUS server (and to work with E on
this).

>Do you really want to write your own RADIUS server?

Oh, of course not!  We're going to use FreeRadius.

We're just putting some other stuff on there as well.  If you could help
E get everything up and running, that would be great.    

Actually, let me put you in contact with "E" and Bob.  They'll be able
to explain a bit, and get you up to speed on what we're doing.

What I need your "expertise" is for the RADIUS server (the
authentication server).  Maybe "coach" E along, and help him get
everything up and running.  Then I'll explain the even bigger problem
what we're working on.  ;-)

Are you familiar with BIND at all?

     Mark

P.S. Our authentication servers need this:

1) Linux
2) FreeRadius
3) MySQL (to store the user accounts)
4) NoCat (to act as a Captive Portal/WI-FI authentication)

Actually, let me give you a brief "synopsis" of how things work.

1) There will be an authentication server (FreeRADIUS)
2) There will be "meshboxes" which are set top boxes for surfing the
internet, etc.  These boxes also act as wireless "Access Points" on the
mesh network.
3) There will be "roaming clients" (PDA's, laptops, etc.) that will use
the MeshBox's to connect to the internet.


I believe we should use something like this:

1) Setup authentication server (RADIUS).
2) MeshBox's authenticate to Authentication Server via 802.1x.  
3) User database is stored on authentication server. (along with
login/passwords)
4) Roaming users, come in contact with a meshbox... the "captive portal"
requests authentication from the wireless user.  The login/password is
entered into the "splash page".  This request (from the wireless side)
is sent via the Ethernet side to the authentication server.  If the
authentication server verifies that the user login/password is correct
then it allows the WI-FI user to connect/use the network (and surf the
web, send mail, etc.)

The problem I'm having (and looking to you for advice) is NOT the WIFI
side, this is already done.  It's the "backbone" side between meshboxes
and the authentication (FreeRADIUS) server(s).  What do you suggest that
we use?  802.1x, correct?

We need help setting it up (E, read the FreeRadius docs) and we need to
make sure that the backbone (between meshbox & auth server) is as secure
as humanly possible.  We need to make sure that the network couldn't
"hi-jacked", or a rogue meshbox (or wireless user) couldn't sniff/steal
passwords or join the network.

          Mark


-----Original Message-----
From: Andy Walden [mailto:an...@ti...] 
Sent: Monday, February 24, 2003 8:11 AM
To: Mark Malewski
Subject: RE: [sg-dc] Radius stuff...

On Mon, 24 Feb 2003, Mark Malewski wrote:

> <Laughing>  Oh... you'll see!  Give me a few days, I'm trying to sort
> through some much write now (too much on my plate at the moment).  But
> I'm going to put you on a team... and have you help lead the
development
> of our RADIUS authentication server.

Do you really want to write your own RADIUS server?

> I'll explain all the details, just let me sort through my mailbox...

Okay.

> Did you join the mailing lists?  I'll ask Bob, and E, to contact
you...
> and "bring you up to speed" on what we're doing.

Yes. Thanks.

andy

--
PGP Key Available at http://www.tigerteam.net/andy/pgp

[MeshBox-radius] meshbox.org:SourceForge.net signing up for MeshBox tasks

[Bob L. <bob...@ho...>]

E

Can you go to:

http://sourceforge.net/pm/?group_id=73855

and sign up for your tasks please. Oh and any others that take your fancy. 
Unfortunately there isn't currently one for 'meshbox destructive HD testing' 
:-)

You'll need to sign in to SourceForge first by the way. If you have any 
problems let me know.

freeRADIUS
IP Allocation
Community IM
MeshServer
Community Locator
Node Display
Ping Triangulation

Bob

> > >I ultimately concluded that the new, out-of-the-box, Maxtor HD was
> > >defective :)  I am going to pick up another on today, and try an
> > make
> > >amends with the Debian spirits...  I will keep you posted.
> >
> > That is unbelievable bad luck, the return rate is probably 1 in 1000
> > at
> > most!
>
>Yes, I couldn't it believe either.  That is why I tried so many
>different approaches.  I blame MS for planting the seeds of OS distrust
>;)
>
>Of course the story doesn't get better.  I went out today and got a new
>WD HD.  My annoyance at finding a cheaper drive as I was walking out of
>the story _in_ the store flyer, was soon over shadowed by the fact that
>this drive also failed to work!!  I now suspect the controller, or the
>fact that I did not listen to my teachers when they told me not to eat
>paste...
>
>E.


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

[MeshBox-radius] RE: meshbox.org:Dynamic Node Mapping/Triangulation projects-:update1

[efstratios g. <efs...@ya...>]

> >I ultimately concluded that the new, out-of-the-box, Maxtor HD was
> >defective :)  I am going to pick up another on today, and try an
> make
> >amends with the Debian spirits...  I will keep you posted.
> 
> That is unbelievable bad luck, the return rate is probably 1 in 1000
> at 
> most!

Yes, I couldn't it believe either.  That is why I tried so many
different approaches.  I blame MS for planting the seeds of OS distrust
;)  

Of course the story doesn't get better.  I went out today and got a new
WD HD.  My annoyance at finding a cheaper drive as I was walking out of
the story _in_ the store flyer, was soon over shadowed by the fact that
this drive also failed to work!!  I now suspect the controller, or the
fact that I did not listen to my teachers when they told me not to eat
paste...

E.