Mesh/Firmware/Overview - Revision history

Redconfetti: Redconfetti moved page Mesh/SudoWRT Tour to Mesh/Firmware/Overview: overview for misc notes and links to other more detailed pages

2016-05-06T04:02:03Z

Redconfetti moved page Mesh/SudoWRT Tour to Mesh/Firmware/Overview: overview for misc notes and links to other more detailed pages

← Older revision	Revision as of 21:02, 5 May 2016
(No difference)

Redconfetti: Redconfetti moved page Mesh/Home Node Internals to Mesh/SudoWRT Tour: trying to find appropriate place for these notes

2016-05-06T04:00:43Z

Redconfetti moved page Mesh/Home Node Internals to Mesh/SudoWRT Tour: trying to find appropriate place for these notes

← Older revision	Revision as of 21:00, 5 May 2016
(No difference)

Redconfetti at 03:45, 6 May 2016

2016-05-06T03:45:46Z

← Older revision		Revision as of 20:45, 5 May 2016
Line 1:		Line 1:
	~~= Accessing Home Node via SSH =~~

	~~Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server.~~

	~~== Ethernet Port ==~~

	~~The 4 Ethernet ports that are provided with your router should be configured as follows:~~

	~~# Private network with DHCP of 172.30.0.x network addresses~~
	~~# Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)~~
	~~# NotDHCP for Extender 1~~
	~~# NotDHCP for Extender 2~~

	~~[https://github.com/sudomesh/notdhcp NotDHCP] is a network configuration service developed by SudoMesh for the extender antennas.~~

	~~This may not apply to your router. For instance, the TP-Link N750 uses the opposite port assignment, with port 3 for private network, and port 4 for public SudoMesh/PeoplesOpen.net network.~~

	~~== Network Settings ==~~

	~~The private network configuration uses the 172.30.0.x network. You should be able to rely on DHCP, or configure a static IP address within this network by using the following settings.~~

	* IP Address: 172.30.0.9
	* Netmask: 255.255.255.0
	* Gateway: 172.30.0.1

	~~See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]~~

	~~== Default Build Configuration ==~~

	The IP address of your home node is <tt>172.22.0.1</tt> prior to configuration via the [https://github.com/sudomesh/makenode makenode] utility. You can SSH into the node as <tt>root</tt> using the password 'meshtheplanet'.

	~~== Post Makenode Configuration ==~~

	~~The IP of your home node on the private network is <tt>172.30.0.1</tt>, with the root password you specified when running <tt>makenode</tt> to configure it.~~

	~~ssh root@172.30.0.1~~
	~~The authenticity of host '172.30.0.1 (172.30.0.1)' can't be established.~~
	~~RSA key fingerprint is b8:9d:4a:2f:1b:f5:e1:ae:b8:19:5b:70:92:8b:7f:34.~~
	~~Are you sure you want to continue connecting (yes/no)?~~

	~~After accepting the key by entering 'yes' and pressing ENTER, it will ask you for the root password.~~

	~~== SSH Keys ==~~

	If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

	= OpenWRT Build =		= OpenWRT Build =

Redconfetti: /* OpenWRT Build */

2016-05-06T03:44:13Z

OpenWRT Build

← Older revision		Revision as of 20:44, 5 May 2016
Line 47:		Line 47:
	= OpenWRT Build =		= OpenWRT Build =

	The SudoMesh project maintains firmware builds for a certain set of Wireless routers (home nodes) and extender antennas. The code used to create these builds is available in [https://github.com/sudomesh/sudowrt-firmware SudoWRT-Firmware]. ~~These firmware builds are a~~		The SudoMesh project maintains firmware builds for a certain set of Wireless routers (home nodes) and extender antennas. The code used to create these builds is available in [https://github.com/sudomesh/sudowrt-firmware SudoWRT-Firmware].

	== Included Software Packages ==		== Included Software Packages ==
Line 55:		Line 55:
	* Home Node Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages openwrt_config/packages].		* Home Node Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages openwrt_config/packages].
	* Extender Antenna Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages.extender-node openwrt_config/packages.extender-node]		* Extender Antenna Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages.extender-node openwrt_config/packages.extender-node]

	~~=== libopenssl ===~~

	~~[libopenssl]~~

	=== uhttpd ===		=== uhttpd ===

	[https://wiki.openwrt.org/doc/howto/http.uhttpd uhttpd] is an efficient and stable web server daemon, suitable for lightweight tasks commonly used with embedded devices and proper integration with [https://wiki.openwrt.org/doc/uci OpenWrt's configuration framework (UCI)]. In particular, it is configured by default for the [https://wiki.openwrt.org/doc/techref/luci LuCI web interface] to administer OpenWrt.		[https://wiki.openwrt.org/doc/howto/http.uhttpd uhttpd] is an efficient and stable web server daemon, suitable for lightweight tasks commonly used with embedded devices and proper integration with [https://wiki.openwrt.org/doc/uci OpenWrt's configuration framework (UCI)]. In particular, it is configured by default for the [https://wiki.openwrt.org/doc/techref/luci LuCI web interface] to administer OpenWrt. SudoMesh uses it's own [https://github.com/sudomesh/sudowrt-web-ui SudoWRT-Web-UI], see [[Mesh/Firmware/Web_Admin_Development]] for more information.

	=== uhttpd-mod-ubus ===		=== uhttpd-mod-ubus ===

Redconfetti: /* Included Software Packages */

2016-05-06T03:32:43Z

Included Software Packages

← Older revision		Revision as of 20:32, 5 May 2016
Line 53:		Line 53:
	The SudoWRT-Firmware code contains a configured list of software packages that are included within the builds for home nodes and the extender antennas.		The SudoWRT-Firmware code contains a configured list of software packages that are included within the builds for home nodes and the extender antennas.

	* Home Node Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages openwrt_config/packages]. * Extender Antenna Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages.extender-node openwrt_config/packages.extender-node]		* Home Node Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages openwrt_config/packages].
			* Extender Antenna Packages - [https://github.com/sudomesh/sudowrt-firmware/blob/master/openwrt_config/packages.extender-node openwrt_config/packages.extender-node]

	=== libopenssl ===		=== libopenssl ===

Redconfetti: /* Ethernet Port */

2016-05-06T03:32:00Z

Ethernet Port

← Older revision		Revision as of 20:32, 5 May 2016
Line 7:		Line 7:
	The 4 Ethernet ports that are provided with your router should be configured as follows:		The 4 Ethernet ports that are provided with your router should be configured as follows:

	1. Private network with DHCP of 172.30.0.x network addresses		# Private network with DHCP of 172.30.0.x network addresses
	2. Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)		# Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)
	3. NotDHCP for Extender 1		# NotDHCP for Extender 1
	4. NotDHCP for Extender 2		# NotDHCP for Extender 2

	[https://github.com/sudomesh/notdhcp NotDHCP] is a network configuration service developed by SudoMesh for the extender antennas.		[https://github.com/sudomesh/notdhcp NotDHCP] is a network configuration service developed by SudoMesh for the extender antennas.

Redconfetti: Redconfetti moved page Mesh Home Node Internals to Mesh/Home Node Internals: consistent use for mesh page naming convention

2016-05-06T03:26:56Z

Redconfetti moved page Mesh Home Node Internals to Mesh/Home Node Internals: consistent use for mesh page naming convention

← Older revision	Revision as of 20:26, 5 May 2016
(No difference)

Redconfetti at 03:25, 6 May 2016

2016-05-06T03:25:17Z

@@ Line 44: / Line 44: @@
 If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.
 = Discovering Network Configuration =
@@ Line 91: / Line 117: @@
 SudoMesh uses a modified version of [https://github.com/sudomesh/babeld babeld], with support for adding or removing interfaces while babeld is running added.
-== Exit Node ==
+= Exit Node =
 Every home node routes traffic to the exit node that was setup for PeoplesOpen.net. This exit node acts as the gateway from the Virtual Private Network (VPN) used by PeoplesOpen.net to contain the SudoMesh network to the Internet.

Redconfetti: /* Debugging */

2016-05-06T02:47:22Z

Debugging

← Older revision		Revision as of 19:47, 5 May 2016
Line 79:		Line 79:
	uci show notdhcpserver[0].addresses		uci show notdhcpserver[0].addresses

	= ~~Debugging~~ =		= Babeld =

	Babel provides the entire routing table for the network.		[https://wiki.openwrt.org/doc/uci/babeld Babel] provides the entire routing table for the network.

	babeld -i		babeld -i

	This provides you with the data on every node on the entire network. ~~Everything~~ connected to the mesh that you can reach will be listed ~~(nodes and extender nodes, not hosts)~~.		This provides you with the data on every node on the entire network. Every node and extender node connected to the mesh that you can reach will be listed. babeld is the daemon that broadcasts routes that are available via the ad-hoc network connection (pplsopen.net-node2node). The age shown in the output provides how long ago the node announced it's existence on the network. When a node becomes too old, it gets dropped from the table.

	~~babel~~ is the daemon that broadcasts routes that are available via the ad-hoc network connection. The age provides how long ago the node announced it's existence. When a node becomes too old, it gets dropped from the table.

	The mesh node will always try to route via the node that has the lowest metric. It tracks the metric also. The 'nexthop' value helps provide information used for routing. It's very lightweight, not complex.		The mesh node will always try to route via the node that has the lowest metric. It tracks the metric also. The 'nexthop' value helps provide information used for routing. It's very lightweight, not complex.

	~~We're using~~ a modified version of ~~babel. It wasn't possible to dynamically configure babel while it is running, so we added that feature~~. ~~Right now your mesh node is routing traffic to the exit node that SudoMesh~~ / ~~PeoplesOpen.net setup, which is the gateway from the VPN to the Internet.~~		SudoMesh uses a modified version of [https://github.com/sudomesh/babeld babeld], with support for adding or removing interfaces while babeld is running added.

	~~== Extender Node ==~~

	~~In the sudowrt-firmware code on Github, there is a file under openwrt_config~~/~~packages.extender-node contains the packages that are installed in the extender node.~~

	~~libopenssl~~, ~~uhttpd and uttpd-mod-ubus (module~~ for ~~uhttpd that acts as proxy between HTTP interface and local ubus,~~ running ~~on port 80)~~

	~~It would be ideal to have an SSL between. Marc has this ready, he'll apply this later after a ubus solution is implemented~~.

	~~You do have to provide a password when accessing the ubus interface. That may not be setup with extender nodes.~~		== Exit Node ==

	~~The extenders are registered with notdhcp, so it would also be best if we could ask notdhcp~~ for the ~~passwords needed to auth and communicate with~~ the ~~ubus HTTP~~. ~~It's currently not possible~~ to ~~ask notdhcp for that information while it's running (but planned~~ to ~~be implemented)~~.		Every home node routes traffic to the exit node that was setup for PeoplesOpen.net. This exit node acts as the gateway from the Virtual Private Network (VPN) used by PeoplesOpen.net to contain the SudoMesh network to the Internet.

Redconfetti at 16:06, 5 May 2016

2016-05-05T16:06:40Z

← Older revision		Revision as of 09:06, 5 May 2016
Line 2:		Line 2:

	Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server.		Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server.

			== Ethernet Port ==

			The 4 Ethernet ports that are provided with your router should be configured as follows:

			1. Private network with DHCP of 172.30.0.x network addresses
			2. Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)
			3. NotDHCP for Extender 1
			4. NotDHCP for Extender 2

			[https://github.com/sudomesh/notdhcp NotDHCP] is a network configuration service developed by SudoMesh for the extender antennas.

			This may not apply to your router. For instance, the TP-Link N750 uses the opposite port assignment, with port 3 for private network, and port 4 for public SudoMesh/PeoplesOpen.net network.

	== Network Settings ==		== Network Settings ==

	The private network configuration uses the 172.22.0.x network.		The private network configuration uses the 172.30.0.x network. You should be able to rely on DHCP, or configure a static IP address within this network by using the following settings.

	~~Reconfigure your machine to use the following network settings, then connect it to Ethernet port 1 to connect on the local private network interface.~~		* IP Address: 172.30.0.9

	* IP Address: 172.22.0.9
	* Netmask: 255.255.255.0		* Netmask: 255.255.255.0
	* Gateway: 0.0.0.0		* Gateway: 172.30.0.1

	See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]		See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]
Line 34:		Line 45:
	If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.		If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

	= Discovering ~~Interfaces~~ =		= Discovering Network Configuration =

			== IP ==

			Run <tt>ip addr show</tt> to discover the IP addresses assigned to your home node.

			== IW ==

	~~Run <tt>ip addr show</tt> to discover the IP addresses assigned to your home node.~~ Use <tt>iw ~~addr show~~</tt> to ~~see~~ the wireless interfaces that are configured.		Use <tt>iw</tt> to inspect the wireless interfaces that are configured.

	<tt>iw phy</tt> will display physical interfaces and capabilities, seeing each radio that is available.		<tt>iw phy</tt> will display physical interfaces and capabilities, seeing each radio that is available.