Pretoria Mesh - Revision history

Kingdavid at 20:24, 25 August 2006

2006-08-25T20:24:53Z

← Older revision		Revision as of 22:24, 25 August 2006
Line 205:		Line 205:
	1. d2:88:6e:34:21:77		1. d2:88:6e:34:21:77
	2. 26:46:6F:34:21:73		2. 26:46:6F:34:21:73


			= Network Log 25 August 2006 =

			Marelie's link has disappeared for about 20 days now due to a fault with the NDIS driver on the water tower (soon to be replaced). But it has reappeared again with BSSID: 26:46:6F:34:21:73. I've locked my node and her node to this BSSID again - maybe the link will hold out until Johann replaces the old soekris boards with the shiny new wrap boards with 802.11a links back to the koppie.

Kingdavid at 20:21, 25 August 2006

2006-08-25T20:21:59Z

← Older revision		Revision as of 22:21, 25 August 2006
Line 1:		Line 1:
	The CSIR Pretoria mesh network was setup as a test-bed mesh network in order to get an understanding of the issues that face real-world, outdoor mesh networks. Some of these issues include [[LOS]] (Line of Sight), [[Weather Proofing]] and the [[Hidden Node]] problem.		The CSIR Pretoria mesh network was setup as a test-bed mesh network in order to get an understanding of the issues that face real-world, outdoor mesh networks. Some of these issues include [[LOS]] (Line of Sight), [[Weather Proofing]] and the [[Hidden Node]] problem.

	Below is a diagram showing the current status of the mesh network, green nodes show people who are currently connected, red nodes show people who would like to be connected in the future		Below is a diagram showing the current status of the mesh network, green nodes show people who are currently connected, red nodes show people who would like to be connected in the future but still have line of sight issues. Yellow shows people who can have requested a connection and can potentially connect

	[[Image:pretoria-mesh-august-small.jpg]]		[[Image:pretoria-mesh-august-small.jpg]]

Kingdavid at 20:21, 25 August 2006

2006-08-25T20:21:03Z

← Older revision		Revision as of 22:21, 25 August 2006
Line 3:		Line 3:
	Below is a diagram showing the current status of the mesh network, green nodes show people who are currently connected, red nodes show people who would like to be connected in the future		Below is a diagram showing the current status of the mesh network, green nodes show people who are currently connected, red nodes show people who would like to be connected in the future

	[[Image:~~Pta~~-~~mesh3~~.jpg]]		[[Image:pretoria-mesh-august-small.jpg]]

Kmatthee: /* Nodes */

2006-08-25T11:22:25Z

Nodes

← Older revision		Revision as of 13:22, 25 August 2006
Line 14:		Line 14:
	[[Koppie Node]]		[[Koppie Node]]

	[[~~Rodricks~~ Node]]		[[Rodericks Node]]

	[[Davids Node]]		[[Davids Node]]

Kmatthee: /* Nodes */

2006-08-17T22:56:28Z

Nodes

← Older revision		Revision as of 00:56, 18 August 2006
Line 10:		Line 10:
	=Nodes=		=Nodes=

	~~***~~Please fill in information about your node e.g. Equipment, Placement (Rooftop), Hardware etc.		Please fill in information about your node e.g. Equipment, Placement (Rooftop), Hardware etc.

	[[Koppie Node]]		[[Koppie Node]]

Kingdavid: /* Network Log 27 July 2006 */

2006-07-27T20:31:25Z

Network Log 27 July 2006

← Older revision		Revision as of 22:31, 27 July 2006
Line 203:		Line 203:
	BSSID's I've seen:		BSSID's I've seen:

	1. d2:88:6e:34:21:77		1. d2:88:6e:34:21:77
	2. 26:46:6F:34:21:73		2. 26:46:6F:34:21:73

Kingdavid at 20:31, 27 July 2006

2006-07-27T20:31:05Z

← Older revision		Revision as of 22:31, 27 July 2006
Line 196:		Line 196:

	The ETX varies between 1.1 and 1.25 which is not bad for an 8km link		The ETX varies between 1.1 and 1.25 which is not bad for an 8km link

			= Network Log 27 July 2006 =

			Mesh partitioning problem isolated Marelie from the net. Cleared BSSID from all the nodes, reset water tower and all nodes, fixed again - but need a better solution.

			BSSID's I've seen:

			1. d2:88:6e:34:21:77
			2. 26:46:6F:34:21:73

Kingdavid: /* Network Log 26 July 2006 */

2006-07-26T20:53:32Z

Network Log 26 July 2006

← Older revision		Revision as of 22:53, 26 July 2006
Line 181:		Line 181:
	We went to the plot today to put the Grid antenna on the high bluegum pole. Thanks to Craig Taylor's Cherry picker I didn't have to hang 12m up in the air on a very wobbly pole.		We went to the plot today to put the Grid antenna on the high bluegum pole. Thanks to Craig Taylor's Cherry picker I didn't have to hang 12m up in the air on a very wobbly pole.

	All went well: A new outdoor router (old aluminium box type) and 24dBi grid we mounted on a metal pole with bottom bracket at the top of the bluegum pole. The cherry picker (an old 60's bedform army truck operated by a Rastafarian) which lifted us to the top of the pole was great fun.		All went well: A new outdoor router (old aluminium box type) and 24dBi grid was mounted on a metal pole with bottom bracket at the top of the bluegum pole. The cherry picker (an old 60's bedform army truck operated by a Rastafarian) which lifted us to the top of the pole was great fun.

	= Network Log 26 July 2006 =		= Network Log 26 July 2006 =

Kingdavid: /* Network Log 26 July 2006 */

2006-07-26T20:52:58Z

Network Log 26 July 2006

← Older revision		Revision as of 22:52, 26 July 2006
Line 179:		Line 179:
	Marelie's antenna moved to a higher pole		Marelie's antenna moved to a higher pole

	We ~~wnet~~ to the plot today to put the Grid antenna on the high bluegum pole. Thanks to Craig Taylor's Cherry picker I didn't have to hang 12m up in the air on a very wobbly pole.		We went to the plot today to put the Grid antenna on the high bluegum pole. Thanks to Craig Taylor's Cherry picker I didn't have to hang 12m up in the air on a very wobbly pole.

	All went well: A new outdoor router (old aluminium box type) and 24dBi grid we mounted on a metal pole with bottom bracket at the top of the bluegum pole. The cherry picker (an old 60's bedform army truck operated by a Rastafarian) which lifted us to the top of the pole was great fun.		All went well: A new outdoor router (old aluminium box type) and 24dBi grid we mounted on a metal pole with bottom bracket at the top of the bluegum pole. The cherry picker (an old 60's bedform army truck operated by a Rastafarian) which lifted us to the top of the pole was great fun.

Kingdavid at 20:52, 26 July 2006

2006-07-26T20:52:38Z

← Older revision		Revision as of 22:52, 26 July 2006
Line 175:		Line 175:
	The strange ssid problem on Elardus Park is apparently just a bug in the reporting tool of FreeBSD		The strange ssid problem on Elardus Park is apparently just a bug in the reporting tool of FreeBSD

			= Network Log 26 July 2006 =

	~~* HELP *~~		Marelie's antenna moved to a higher pole

	~~PERHAPS NOT THE CORRECT PLACE TO POST THIS MESSAGE BUT COULD ANYONE ASSIST IN CONNECTING TO THE ELARDUSPARK TOWER~~.		We wnet to the plot today to put the Grid antenna on the high bluegum pole. Thanks to Craig Taylor's Cherry picker I didn't have to hang 12m up in the air on a very wobbly pole.

	~~I'M ABOUT 1 KM FROM THE TOWER HOWEVER DON~~'~~T HAVE LINE OF SIGHT. IT WOULD APPEAR THAT I NEED TO HAVE LINE OF SIGHT, OTHERWISE MY 802.11 CARD WONT PICK UP PTAMESH~~.		All went well: A new outdoor router (old aluminium box type) and 24dBi grid we mounted on a metal pole with bottom bracket at the top of the bluegum pole. The cherry picker (an old 60's bedform army truck operated by a Rastafarian) which lifted us to the top of the pole was great fun.

	~~ANY HELP MUCH APREACIATED.~~		= Network Log 26 July 2006 =

	~~hvrensburgATigrade~~.co.za		Optimized some networking settings

			I discovered the value of setting the BSSID and the fragmentation threshold

			I noticed that Marelie's link was giving good ping times but performing badly with larger data loads. The framentation threshold allows you to set the threshold in bytes at which point a data block is split up into seperate TCP/IP fragments. With Marelie being a hidden node, and a large amount of interference possible. I set the fragmentation threshold to its lowest at 256 instead of the default 2346.

			And yipppeee! the link is far more reliable

			I also set the BSSID to d2:88:6e:34:21:77 which is what the rest of the network connected to the elardus park water tower is using and this also made a big difference in the network stability.

			The ETX varies between 1.1 and 1.25 which is not bad for an 8km link