Actions

Byzantium Sprint 1: Difference between revisions

From HacDC Wiki

No edit summary
m (Reverted edits by Cheaptara (talk) to last revision by Drwho)
Line 1: Line 1:
In the present marketplace purchasers can uncover just about any merchandise founded to order http://www.botanicalslimmingstore.com/diet_pills_diet.htm by means of the capuccino we consume for the desktops we buy,
Goal - Reliably bridge two different and separate wireless networks without using existing internet infrastructure.
purchasers are in a placement to pick and choose the capabilities http://www.botanicalslimmingstore.com/ they would want to ensure the products they purchase fulfill their exact specifications.
 
Modern capuccino chains can possibly be credited http://www.cheapdiscounttiffanystore.com/tiffany-usa.html with commencing the tendency of 'made to order.'
Design goals
troll in to any capuccino shop http://www.cheapdiscounttiffanystore.com/tiffany-and-co-necklaces.html whether or not it is in actuality an enormous chain or small online community store,
1) There should be a webserver on each network providing a service of some kind (microblogs, web chat, file dump).
and each and every and every menu product http://www.cheapdiscounttiffanystore.com/genuine-tiffany.html could possibly be adjusted every your specifications.
2) Nodes in either network should be able to reach both webservers.
3) Nodes on one network should be able to talk to nodes on the other network and vice versa.
4) Networks should have at least 3-5 nodes each.
 
Tentative schedule is as follows:
 
Friday - 8:00pm Pizza and planning (any particular request should email me off list).  (COMPLETE!)
Saturday - 9:00am Start showing up  (IN PROGRESS!)
Saturday - 10:00am Divide into groups and start the sprint.
Sunday - 10:00am Start showing up.
Sunday - 11:00am Finish the sprint!
Sunday - Evening Debriefing (I'll be taking extensive notes to update the wiki).
 
Notes:
*[[BATMAN]]
*[[BATMAN-Advanced Setup]]
*[[Babel]]
*[[Babel Setup]]
 
Plans!
We're gonna have two teams each will implement a mesh network using some existing mesh protocol. One team will be working with BATMAN-Advanced and the other with BABEL. Each network will use at least one openwrt device the rest will be laptops and netbooks.
 
from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]
[http://p2pfoundation.net/Mesh_Networks From p2pfoundation.net]
 
Interesting threads:
[http://lists.alioth.debian.org/pipermail/babel-users/2008-August/000151.html A few comments on the BATMAN routing protocol]
[http://lists.alioth.debian.org/pipermail/babel-users/2008-August/000156.html A few more comments on the BATMAN routing protocol]
[http://www.open-mesh.org/wiki/batman-adv/Tweaking Tweaking BATMAN-adv]
 
=== Distributed DNS ===
see [[Byzantium_Distributed_DNS|this]]

Revision as of 13:16, 11 July 2011

Goal - Reliably bridge two different and separate wireless networks without using existing internet infrastructure.

Design goals 1) There should be a webserver on each network providing a service of some kind (microblogs, web chat, file dump). 2) Nodes in either network should be able to reach both webservers. 3) Nodes on one network should be able to talk to nodes on the other network and vice versa. 4) Networks should have at least 3-5 nodes each.

Tentative schedule is as follows:

Friday - 8:00pm Pizza and planning (any particular request should email me off list). (COMPLETE!) Saturday - 9:00am Start showing up (IN PROGRESS!) Saturday - 10:00am Divide into groups and start the sprint. Sunday - 10:00am Start showing up. Sunday - 11:00am Finish the sprint! Sunday - Evening Debriefing (I'll be taking extensive notes to update the wiki).

Notes:

Plans! We're gonna have two teams each will implement a mesh network using some existing mesh protocol. One team will be working with BATMAN-Advanced and the other with BABEL. Each network will use at least one openwrt device the rest will be laptops and netbooks.

from Wikipedia: Byzantine From p2pfoundation.net

Interesting threads: A few comments on the BATMAN routing protocol A few more comments on the BATMAN routing protocol Tweaking BATMAN-adv

Distributed DNS

see this