[CUWiN] FreeNet Router Project
ian.white at datamile-computers.com
Thu Jan 6 03:40:49 CST 2005
Running my own Locustworld mesh but slightly unhappy about the way the source is
controlled etc, I've been looking at the other projects around.
WRT based ones , seasoft... wifidog
PC based ones like cuwin.
Having seen the benefits of a large number of developers working and testing on
a OS project (xoops/postnuke), I wonder why the wireless mesh world is so
1) 11b/11g support
2) nodes capable of dynamic meshing and routing
3) User authorization (nocat in most cases), and vpn support for users
4) inter-node security/firewall (vpn or certs)
5) traffic control, dianogtics and limits
and most of the stuff is open source and just needs taping together.
The only main difference appears to be routing algorithm, and in theory thats a
Quoting Dan Flett <conhoolio at hotmail.com>:
> Hi All,
> I've started a Wiki page detailing a project I am working on. I am
> seeking advice, criticism, or contributions of any sort on this.
> In short, I'm aiming to create a cheap, dual radio "router-in-a-box"
> with a user friendly web interface - with the aim of making it
> mass-producable. On the wiki page above the various existing hardware
> and software options are investigated.
> I'm involved with Melbourne Wireless
> (http://www.melbournewireless.org.au) where we aim to make a standalone
> wireless network across the city. Australian Government regulations
> restrict the ways in which you can distribute Internet access - hefty
> licence fees are involved - so our network aims to be a city-wide
> wireless intranet, not necessarily using landlines or any sort of
> Internet tunnelling to connect network clusters. The 'network
> administrators' are the node owners, most of whom are not network
> engineers, hence the need for a user friendly web interface on the
> The FreeNet Router Project Wiki page specifies a generic router design,
> but I would anticipate that the various FreeNet and Community Wireless
> groups around the world would want to customise it to suit local
> conditions - both from a hardware and a software perspective.
> If you're interested in contributing, please email me, or just add your
> contributions to the Wiki page.
> Dan Flett
> CU-Wireless mailing list
> CU-Wireless at lists.cuwireless.net
> Project Page: http://cuwireless.ucimc.org
More information about the CU-Wireless