High performance node page - Revision history

Ajay: Replacing page with 'migrated to wireless dev'

2009-06-17T14:27:40Z

Replacing page with 'migrated to wireless dev'

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T13:47:19Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 15:47, 21 May 2009
Line 86:		Line 86:

	Future improvements:		Future improvements:
	- In scenarios where connectivity is possible to another node, on both the panel and omni, then our current algorithm will always select the panel, even if the omni may be a better choice.		- In scenarios where connectivity is possible to another node, on both the panel and omni,
			then our current algorithm will always select the panel, even if the omni may be a better choice.

	* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be override via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.		* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be override via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T13:46:29Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 15:46, 21 May 2009
Line 75:		Line 75:
	A HPN node will always start to search for connectivity on the panel antenna, fist on the same colour as the node, and then on the other colour. If no connectivity can be found, then it will hunt on the omni-directional antenna, first on opposite colour as the node, and then on the same colour. This sequence will repeat itself, until connectivity can be found to another node in the network. At this time the channels will be locked the colour of the node will be the same as the colour used on the panel antenna. This setting will stay the same, even across a reboot or power failure, until someone overrides it via the web interface.		A HPN node will always start to search for connectivity on the panel antenna, fist on the same colour as the node, and then on the other colour. If no connectivity can be found, then it will hunt on the omni-directional antenna, first on opposite colour as the node, and then on the same colour. This sequence will repeat itself, until connectivity can be found to another node in the network. At this time the channels will be locked the colour of the node will be the same as the colour used on the panel antenna. This setting will stay the same, even across a reboot or power failure, until someone overrides it via the web interface.

	Lets take a new GREEN node for a example. When it boots up for the first time then it will come up in the hunting mode. It will first configure the patch antenna on the "green" ~~frequency~~. It will perform a link local IPv6 ping on that interface for about 3 seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after 3 seconds, then it will hunt further using the "red" channel on the patch, then ~~the~~ "red" ~~channel~~ on the omni and then "green" on the omni.		Lets take a new GREEN node for a example. When it boots up for the first time then it will come up in the hunting mode. It will first configure the patch antenna on the "green" channel. Then it will perform a link local IPv6 ping on that interface for about 3 seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after 3 seconds, then it will hunt further using the "red" channel on the patch, then "red" on the omni and then "green" on the omni.

	If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB interface. If connectivity can be established, then it will lock the node with the current settings. It will also enable the green/red link LED on the bottom of the node to show connectivity on that channel (The WEB interface can be used to get more information of which node connectivity has been established to). If connectivity is lost then the LED will turn off again.		If no connectivity can be found, then it will start the hunting process from the beginning again, or until it is manually locked via the WEB interface. If connectivity can be established, then it will lock the node with the current settings. It will also enable the green/red link LED on the bottom of the node to show connectivity on that channel (The WEB interface can be used to get more information of which node connectivity has been established to). If connectivity is lost then the LED will turn off again.

	See hunt-flow-diagram below.		See hunt-flow-diagram below.

	[[Image:Hunt-flow2.png]]		[[Image:Hunt-flow2.png]]

			Note that this hunting procedure does not always end up in the best routing solution and it is not a replacement for common sense.

			Future improvements:
			- In scenarios where connectivity is possible to another node, on both the panel and omni, then our current algorithm will always select the panel, even if the omni may be a better choice.

	* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be override via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.		* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be override via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T13:27:23Z

Behaviour of a normal node in a mesh

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T13:24:54Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 15:24, 21 May 2009
Line 65:		Line 65:
	== Behaviour of a normal node in a mesh ==		== Behaviour of a normal node in a mesh ==

	~~[[Initial~~ (~~old~~) ~~hunting description]]~~		The following describes how a normal node will behave inside a mesh and what service it will provide:

			* Each HPN node is equipped with two 5.8Ghz wifi adapters and antennas (pannel and omni) that is used to build the backbone. Each one of these adapters is configured to operate on a specific wifi frequency that is also tied to a specific wifi channel. In order to make our HPN more user friendly we decided to assign these two channels to the colours "red" and "green". The HPN node then inherit what ever colour is assigned to the directional pannel antenna on the front.

			This means that when the "green" channel is configured on the pannel antenna, then the "red" is used on the omni and we will refer to the HPN node as a GREEN node. If the "red" channel is used on the pannel, then we talk about a RED node and the "green channel is used on the omni. The default setting for a new node is to be a GREEN node and it can be changed to a RED node via the web interface.

	The following describes ~~how~~ a ~~normal~~ node will ~~behave inside~~ a ~~mesh~~ and ~~what service~~ it will ~~provide:~~		When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. There are lots of possible different ways to do this hunting. We decided to implement a very simple and easy algorithm until someone gets 'n new bright ideas. The following paragraphs describes our current implementation of our hunting procedure with our [[Initial (old) hunting description]] here.

			A HPN node will always start to search for connectivity on the pannel antenna, fist on the same colour as the node, and then on the other colour. If no connectivity can be found, then it will hunt on the omni-directional antenna, first on opposite colour as the node, and then on the same colour. This sequence will repeat itself, until connectivity can be found to another node in the network. At this time the channels will be locked the colour of the node will be the same as the colour used on the pannel antenna. This setting will stay the same, even across a reboot or power failure, until someone overrides it via the web interface.

			Lets take a new GREEN node for a example. When it boots up for the first time then it will come up in the hunting mode. It will first configure the patch antenna on the "green" frequency. It will perform a link local IPv6 ping on that interface for about 3 seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after 3 seconds, then it will hunt further using the "red" channel on the patch, then the "red" channel on the omni and then "green" on the omni.

			If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB interface. If connectivity can be established, then it will lock the node with the current settings. It will also enable the green/red link LED on the bottom of the node to show connectivity on that channel (The WEB interface can be used to get more information of wich node connectivity has been established to). If connectivity is lost then the LED will turn off again.

	* When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. In hunting mode it will first configure the patch antenna on the GREEN frequency. It will perform a link local IPv6 ping on that interface for about X seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after X seconds, then it will hunt further using RED on the patch, then GREEN on the omni and then RED on the omni. If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB terface. If connectivity can be established, then it will enable the green/red link LED on the bottom of the node to show connectivity (use the WEB interface for more information on to which node connectivity has been established to). If connectivity is lost then the LED will be off again. After stable connectivity for about X consecutive pings, the node will lock the antenna/channels util someone changes it manually via the WEB interface. Once the antennas/channels are locked then it will also change the sensitivity of the link LED and LED updates will be less frequently. The LED sensitivity can be manually changed via the WEB interface by selecting the "alignment" button. The alignment feature will give signal strength information on the WEB interface. See hunt-flow-diagram below.		See hunt-flow-diagram below.

	[[Image:Hunt-flow2.png]]		[[Image:Hunt-flow2.png]]

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T12:26:30Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 14:26, 21 May 2009
Line 71:		Line 71:
	* When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. In hunting mode it will first configure the patch antenna on the GREEN frequency. It will perform a link local IPv6 ping on that interface for about X seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after X seconds, then it will hunt further using RED on the patch, then GREEN on the omni and then RED on the omni. If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB terface. If connectivity can be established, then it will enable the green/red link LED on the bottom of the node to show connectivity (use the WEB interface for more information on to which node connectivity has been established to). If connectivity is lost then the LED will be off again. After stable connectivity for about X consecutive pings, the node will lock the antenna/channels util someone changes it manually via the WEB interface. Once the antennas/channels are locked then it will also change the sensitivity of the link LED and LED updates will be less frequently. The LED sensitivity can be manually changed via the WEB interface by selecting the "alignment" button. The alignment feature will give signal strength information on the WEB interface. See hunt-flow-diagram below.		* When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. In hunting mode it will first configure the patch antenna on the GREEN frequency. It will perform a link local IPv6 ping on that interface for about X seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after X seconds, then it will hunt further using RED on the patch, then GREEN on the omni and then RED on the omni. If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB terface. If connectivity can be established, then it will enable the green/red link LED on the bottom of the node to show connectivity (use the WEB interface for more information on to which node connectivity has been established to). If connectivity is lost then the LED will be off again. After stable connectivity for about X consecutive pings, the node will lock the antenna/channels util someone changes it manually via the WEB interface. Once the antennas/channels are locked then it will also change the sensitivity of the link LED and LED updates will be less frequently. The LED sensitivity can be manually changed via the WEB interface by selecting the "alignment" button. The alignment feature will give signal strength information on the WEB interface. See hunt-flow-diagram below.

	[[Image:Hunt-~~flow-diag~~.png]]		[[Image:Hunt-flow2.png]]

	* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be overrided via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.		* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be overrided via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.

JHugo: /* Initial (old) hunting description */

2009-05-21T12:21:28Z

Initial (old) hunting description

← Older revision		Revision as of 14:21, 21 May 2009
Line 65:		Line 65:
	== Behaviour of a normal node in a mesh ==		== Behaviour of a normal node in a mesh ==

	= [[Initial (old) hunting description]] =		[[Initial (old) hunting description]]

	The following describes how a normal node will behave inside a mesh and what service it will provide:		The following describes how a normal node will behave inside a mesh and what service it will provide:

JHugo: /* Initial (old) hunting description */

2009-05-21T12:21:06Z

Initial (old) hunting description

← Older revision		Revision as of 14:21, 21 May 2009
Line 65:		Line 65:
	== Behaviour of a normal node in a mesh ==		== Behaviour of a normal node in a mesh ==

	== [[Initial (old) hunting description]] ==		= [[Initial (old) hunting description]] =

	The following describes how a normal node will behave inside a mesh and what service it will provide:		The following describes how a normal node will behave inside a mesh and what service it will provide:

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T12:20:38Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 14:20, 21 May 2009
Line 65:		Line 65:
	== Behaviour of a normal node in a mesh ==		== Behaviour of a normal node in a mesh ==

	== [[Initial (old) hunting description]]		== [[Initial (old) hunting description]] ==

	The following describes how a normal node will behave inside a mesh and what service it will provide:		The following describes how a normal node will behave inside a mesh and what service it will provide:

JHugo: /* Behaviour of a normal node in a mesh */

2009-05-21T12:20:25Z

Behaviour of a normal node in a mesh

← Older revision		Revision as of 14:20, 21 May 2009
Line 64:		Line 64:

	== Behaviour of a normal node in a mesh ==		== Behaviour of a normal node in a mesh ==

			== [[Initial (old) hunting description]]

	The following describes how a normal node will behave inside a mesh and what service it will provide:		The following describes how a normal node will behave inside a mesh and what service it will provide:

← Older revision		Revision as of 15:27, 21 May 2009
Line 67:		Line 67:
	The following describes how a normal node will behave inside a mesh and what service it will provide:		The following describes how a normal node will behave inside a mesh and what service it will provide:

	* Each HPN node is equipped with two 5.8Ghz wifi adapters and antennas (~~pannel~~ and omni) that is used to build the backbone. Each one of these adapters is configured to operate on a specific wifi frequency that is also tied to a specific wifi channel. In order to make our HPN more user friendly we decided to assign these two channels to the colours "red" and "green". The HPN node then inherit what ever colour is assigned to the directional ~~pannel~~ antenna on the front.		* Each HPN node is equipped with two 5.8Ghz wifi adapters and antennas (panel and omni) that is used to build the backbone. Each one of these adapters is configured to operate on a specific wifi frequency that is also tied to a specific wifi channel. In order to make our HPN more user friendly we decided to assign these two channels to the colours "red" and "green". The HPN node then inherit what ever colour is assigned to the directional panel antenna on the front.

	This means that when the "green" channel is configured on the ~~pannel~~ antenna, then the "red" is used on the omni and we will refer to the HPN node as a GREEN node. If the "red" channel is used on the ~~pannel~~, then we talk about a RED node and the "green channel is used on the omni. The default setting for a new node is to be a GREEN node and it can be changed to a RED node via the web interface.		This means that when the "green" channel is configured on the panel antenna, then the "red" is used on the omni and we will refer to the HPN node as a GREEN node. If the "red" channel is used on the panel, then we talk about a RED node and the "green channel is used on the omni. The default setting for a new node is to be a GREEN node and it can be changed to a RED node via the web interface.

	When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. There are lots of possible different ways to do this hunting. We decided to implement a very simple and easy algorithm until someone gets 'n new bright ideas. The following paragraphs describes our current implementation of our hunting procedure with our [[Initial (old) hunting description]] here.		When a new node boots up for the fist time, then it will go into a hunting mode and it will search for other nodes in the mesh. There are lots of possible different ways to do this hunting. We decided to implement a very simple and easy algorithm until someone gets 'n new bright ideas. The following paragraphs describes our current implementation of our hunting procedure with our [[Initial (old) hunting description]] here.

	A HPN node will always start to search for connectivity on the ~~pannel~~ antenna, fist on the same colour as the node, and then on the other colour. If no connectivity can be found, then it will hunt on the omni-directional antenna, first on opposite colour as the node, and then on the same colour. This sequence will repeat itself, until connectivity can be found to another node in the network. At this time the channels will be locked the colour of the node will be the same as the colour used on the ~~pannel~~ antenna. This setting will stay the same, even across a reboot or power failure, until someone overrides it via the web interface.		A HPN node will always start to search for connectivity on the panel antenna, fist on the same colour as the node, and then on the other colour. If no connectivity can be found, then it will hunt on the omni-directional antenna, first on opposite colour as the node, and then on the same colour. This sequence will repeat itself, until connectivity can be found to another node in the network. At this time the channels will be locked the colour of the node will be the same as the colour used on the panel antenna. This setting will stay the same, even across a reboot or power failure, until someone overrides it via the web interface.

	Lets take a new GREEN node for a example. When it boots up for the first time then it will come up in the hunting mode. It will first configure the patch antenna on the "green" frequency. It will perform a link local IPv6 ping on that interface for about 3 seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after 3 seconds, then it will hunt further using the "red" channel on the patch, then the "red" channel on the omni and then "green" on the omni.		Lets take a new GREEN node for a example. When it boots up for the first time then it will come up in the hunting mode. It will first configure the patch antenna on the "green" frequency. It will perform a link local IPv6 ping on that interface for about 3 seconds to determine if any IPv6 connectivity can be found on that antenna/channel. If no connectivity is found after 3 seconds, then it will hunt further using the "red" channel on the patch, then the "red" channel on the omni and then "green" on the omni.

	If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB interface. If connectivity can be established, then it will lock the node with the current settings. It will also enable the green/red link LED on the bottom of the node to show connectivity on that channel (The WEB interface can be used to get more information of ~~wich~~ node connectivity has been established to). If connectivity is lost then the LED will turn off again.		If no connectivity can be found, then it will start the hunting process from the beginning, or until it is manually locked via the WEB interface. If connectivity can be established, then it will lock the node with the current settings. It will also enable the green/red link LED on the bottom of the node to show connectivity on that channel (The WEB interface can be used to get more information of which node connectivity has been established to). If connectivity is lost then the LED will turn off again.

	See hunt-flow-diagram below.		See hunt-flow-diagram below.
Line 83:		Line 83:
	[[Image:Hunt-flow2.png]]		[[Image:Hunt-flow2.png]]

	* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be ~~overrided~~ via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.		* When a new node boots up then an unique IPv6 address ((inside this mesh. See IP addressing section) will be configured on all the Ethernet and wireless interfaces. An unique (inside this mesh) IPv4 address is calculated and configured on the Ethernet interface and on the 2.4Ghz omni interface. The node will use the MAC address of the adapter to calculate a unique IPv4 and IPv6 subnet for that interface. These automatic addresses can be override via the WEB interface (E.g. if a globally routeable IPv6 address is required for a website inside the mesh and it should be visible from the Internet). Wireless interfaces are placed into adhoc mode and the channel, ssid and bssid are also configured.

	* When a new node boots up then the OLSR daemon is started and it will listen en send OLSR topology packets to all of it's neighboring nodes. OLSR runs on all the wireless interfaces, but not on the Ethernet interface. All the IPv4 subnets are converted to 4in6 IPv6 addresses and these IPv6 subnets are placed into the HNA section of olsrd.conf, together with the IPv6 subnets that are configured on the Ethernet interface and on the 2.4Ghz omni interface. These HNA subnets are then distributed, via OLSR, to all the other nodes inside the mesh.		* When a new node boots up then the OLSR daemon is started and it will listen en send OLSR topology packets to all of it's neighboring nodes. OLSR runs on all the wireless interfaces, but not on the Ethernet interface. All the IPv4 subnets are converted to 4in6 IPv6 addresses and these IPv6 subnets are placed into the HNA section of olsrd.conf, together with the IPv6 subnets that are configured on the Ethernet interface and on the 2.4Ghz omni interface. These HNA subnets are then distributed, via OLSR, to all the other nodes inside the mesh.

	* The 4over6 tunneling daemon take care of all IPv4 comms and ~~dirtributing~~ of routing information inside the mesh.		* The 4over6 tunneling daemon take care of all IPv4 comms and distributing of routing information inside the mesh.

	* The node will start ntpd daemon on provide NTP time services on all it's IPv4 and IPv6 addresses. NTP will also synchronize it's local time with the GW-node on a regular basis.		* The node will start ntpd daemon on provide NTP time services on all it's IPv4 and IPv6 addresses. NTP will also synchronize it's local time with the GW-node on a regular basis.
Line 99:		Line 99:
	* sshd allows remote ssh login's from anywhere in the mesh network.		* sshd allows remote ssh login's from anywhere in the mesh network.

	* ~~watchdogd~~ toggles the watchdog during normal operations. Should the system hang for some reason, then the watchdog will restart the HPN node.		* watchdog toggles the watchdog during normal operations. Should the system hang for some reason, then the watchdog will restart the HPN node.

	* mini_httpd is used for the WEB gui running on the HPN node.		* mini_httpd is used for the WEB gui running on the HPN node.