Byzantium Sprint 1 - Revision history

ITechGeek at 09:20, 3 April 2012

2012-04-03T09:20:08Z

← Older revision		Revision as of 09:20, 3 April 2012
Line 35:		Line 35:
	=== Distributed DNS ===		=== Distributed DNS ===
	see [[Byzantium_Distributed_DNS\|this]]		see [[Byzantium_Distributed_DNS\|this]]

			{{Template:Byzantium}}

Katie: Reverted edits by Cheaptara (talk) to last revision by Drwho

2011-07-11T13:16:14Z

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,
+) 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.
+) Nodes in either network should be able to reach both webservers.

Cheaptara at 05:52, 11 July 2011

2011-07-11T05:52:21Z

@@ Line 1: / Line 1: @@
-Goal - Reliably bridge two different and separate wireless networks without using existing internet infrastructure.
+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,
+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.
-Design goals
+Modern capuccino chains can possibly be credited	http://www.cheapdiscounttiffanystore.com/tiffany-usa.html	with commencing the tendency of 'made to order.'
-) There should be a webserver on each network providing a service of some kind (microblogs, web chat, file dump).
+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,
-) Nodes in either network should be able to reach both webservers.
+and each and every and every menu product 	http://www.cheapdiscounttiffanystore.com/genuine-tiffany.html	could possibly be adjusted every your specifications.

Drwho at 18:13, 5 May 2011

2011-05-05T18:13:55Z

← Older revision		Revision as of 18:13, 5 May 2011
Line 31:		Line 31:
	[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/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://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 ===		=== Distributed DNS ===
	see [[Byzantium_Distributed_DNS\|this]]		see [[Byzantium_Distributed_DNS\|this]]

Drwho at 18:33, 30 April 2011

2011-04-30T18:33:33Z

← Older revision		Revision as of 18:33, 30 April 2011
Line 1:		Line 1:

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

Line 28:		Line 27:
	from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]		from Wikipedia: [http://en.wikipedia.org/wiki/Byzantine_fault_tolerance#Origin Byzantine]
	[http://p2pfoundation.net/Mesh_Networks From p2pfoundation.net]		[http://p2pfoundation.net/Mesh_Networks From p2pfoundation.net]
	~~[http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 The Doctor's writeup.]~~

	Interesting threads:		Interesting threads:

Haxwithaxe: /* Distributed DNS */

2011-04-13T06:17:37Z

Distributed DNS

← Older revision		Revision as of 06:17, 13 April 2011
Line 35:		Line 35:

	=== Distributed DNS ===		=== Distributed DNS ===
	[~~http://en.wikipedia.org/wiki/Distributed_hash_table Distributed Hash Table (DHT)] - Wikipeda page on DHTs. Has a decent overview of how they work.~~		see [[Byzantium_Distributed_DNS\|this]]

	[~~http://www.bamboo-dht.org/ Bamboo DHT~~] ~~- A DHT implementation in Java.~~

	~~[http://code.google.com/p/upright/ UpRight] - A library for building fault-tolerant distributed systems. Incorporates innovations from modern solutions to Byzantine fault tolerance.~~

	[https://secure.wikimedia.org/wikipedia/en/wiki/Gossip_protocol Gossip Protocols]: Nodes in a network pseudorandomly select peers to exchange information with. Could be useful for distributing the contents of a DHT-based DNS implementation within a mesh network.
	[https://secure.wikimedia.org/wikipedia/en/wiki/Kademlia Kademlia] has an interesting way of handling the entry distribution problem. When inserting an entry, it iterates through the table to find suitable nodes in the network to hold that entry and propagates it to them as well as saving a copy locally.

	[http://conferences.sigcomm.org/sigcomm/2004/papers/p292-ramasubramanian1111.pdf CoDoNS paper] - A very good paper from 2004 on a distributed DNS alternative. It still relies on centralized domain name registration.
	~~[http://www.cs.cornell.edu/people/egs/beehive/codons.php CoDoNS main page] - It appears that CoDoNS is operational and running on PlanetLab.~~
	~~Unfortunately, I don't see any code. I see no reason why we can't simply hijack their design.~~

	~~[http://www.surfnet.nl/Documents/DNSSSEC-web.pdf Tutorial on DNS and DNSSEC]~~

	~~[http://nms.lcs.mit.edu/projects/ins/ Intentional Naming System~~] - "INS is a new naming system intended for naming and discovering a variety of resources in future networks of devices and services. It has the following interesting characteristics about the way it names resources and the way names are resolved."

Haxwithaxe: Created page with " 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 ..."

2011-03-28T16:29:02Z

Created page with " 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 ..."

New page

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:
*[[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]
[http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 The Doctor's writeup.]

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]

=== Distributed DNS ===
[http://en.wikipedia.org/wiki/Distributed_hash_table Distributed Hash Table (DHT)] - Wikipeda page on DHTs. Has a decent overview of how they work.

[http://www.bamboo-dht.org/ Bamboo DHT] - A DHT implementation in Java.

[http://code.google.com/p/upright/ UpRight] - A library for building fault-tolerant distributed systems. Incorporates innovations from modern solutions to Byzantine fault tolerance.

[https://secure.wikimedia.org/wikipedia/en/wiki/Gossip_protocol Gossip Protocols]: Nodes in a network pseudorandomly select peers to exchange information with. Could be useful for distributing the contents of a DHT-based DNS implementation within a mesh network.
[https://secure.wikimedia.org/wikipedia/en/wiki/Kademlia Kademlia] has an interesting way of handling the entry distribution problem. When inserting an entry, it iterates through the table to find suitable nodes in the network to hold that entry and propagates it to them as well as saving a copy locally.

[http://conferences.sigcomm.org/sigcomm/2004/papers/p292-ramasubramanian1111.pdf CoDoNS paper] - A very good paper from 2004 on a distributed DNS alternative. It still relies on centralized domain name registration.
[http://www.cs.cornell.edu/people/egs/beehive/codons.php CoDoNS main page] - It appears that CoDoNS is operational and running on PlanetLab.
Unfortunately, I don't see any code. I see no reason why we can't simply hijack their design.

[http://www.surfnet.nl/Documents/DNSSSEC-web.pdf Tutorial on DNS and DNSSEC]

[http://nms.lcs.mit.edu/projects/ins/ Intentional Naming System] - "INS is a new naming system intended for naming and discovering a variety of resources in future networks of devices and services. It has the following interesting characteristics about the way it names resources and the way names are resolved."