Seattle Meshnet: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
== Develop the SeaMeshBox == | == Develop the SeaMeshBox == | ||
Name is a placeholder. Basically get the whole process of converting a box into a node, installing CJDNS and anything else it needs to function as an easily-managed and secure router, documented. Do benchmarks with each unit, get an idea of what hardware is capable of. Standard install image (maybe a whole distro someday!), etc. Also see about custom cases of some sort (might be best to strip large clunky towers and put the needed components into a smaller case of some kind), using donated wireless routers as AP's or bridges, etc. | Name is a placeholder, unless Dan actually likes it. Basically get the whole process of converting a box into a node, installing CJDNS and anything else it needs to function as an easily-managed and secure router, documented. Do benchmarks with each unit, get an idea of what hardware is capable of. Standard install image (maybe a whole distro someday!), etc. Also see about custom cases of some sort (might be best to strip large clunky towers and put the needed components into a smaller case of some kind), using donated wireless routers as AP's or bridges, etc. | ||
== SeaMeshBox Factory! == | == SeaMeshBox Factory! == | ||
At this point, we've got setting up old boxes as nodes down to an automatic process. We know what kind of incoming hardware is best for this and we can crank out as many as we have suitable donations. How these get distributed is an open question that will require some consultation with Seattle Meshnet. The goal is to have CJDNS routers/meshnet nodes that can be given to businesses and individuals as easily as a new router from an ISP. Easier actually. | At this point, we've got setting up old boxes as nodes down to an automatic process. We know what kind of incoming hardware is best for this and we can crank out as many as we have suitable donations. How these get distributed is an open question that will require some consultation with Seattle Meshnet. The goal is to have CJDNS routers/meshnet nodes that can be given to businesses and individuals as easily as a new router from an ISP. Easier actually. | ||
Revision as of 17:23, 24 April 2014
CJDNS Node/Gateway Router
Will just be hooked up to Hyperboria via a VPN tunnel until a wireless connection with the nodes up towards Capitol Hill can be established.
Meshnet Node
One or more long-range antennas on the roof.
Develop the SeaMeshBox
Name is a placeholder, unless Dan actually likes it. Basically get the whole process of converting a box into a node, installing CJDNS and anything else it needs to function as an easily-managed and secure router, documented. Do benchmarks with each unit, get an idea of what hardware is capable of. Standard install image (maybe a whole distro someday!), etc. Also see about custom cases of some sort (might be best to strip large clunky towers and put the needed components into a smaller case of some kind), using donated wireless routers as AP's or bridges, etc.
SeaMeshBox Factory!
At this point, we've got setting up old boxes as nodes down to an automatic process. We know what kind of incoming hardware is best for this and we can crank out as many as we have suitable donations. How these get distributed is an open question that will require some consultation with Seattle Meshnet. The goal is to have CJDNS routers/meshnet nodes that can be given to businesses and individuals as easily as a new router from an ISP. Easier actually.