[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