Mesh/Firmware/Generating - Revision history

50.0.83.158: /* freifunk */

2013-10-25T05:06:41Z

freifunk

← Older revision		Revision as of 22:06, 24 October 2013
Line 56:		Line 56:

	After looking at the code, I am not inclined to use it. Lots of freifunk-specific stuff. Few comments. In the end, all it does that we really care about is take a few values from the web app, write some config files for openwrt and run "make image" with some parameters. It does have a system for queuing builds, which is nice. Honestly, I think we're going to be better off making our own system		After looking at the code, I am not inclined to use it. Lots of freifunk-specific stuff. Few comments. In the end, all it does that we really care about is take a few values from the web app, write some config files for openwrt and run "make image" with some parameters. It does have a system for queuing builds, which is nice. Honestly, I think we're going to be better off making our own system

			= SQLite =

			SQL Script for meshnode database:
			<pre>
			BEGIN TRANSACTION;
			CREATE TABLE node (model TEXT, version TEXT, id TEXT, rsakeypair TEXT, dsakeypair TEXT, ecdsakeypair TEXT, rootkeypair TEXT, geoloc TEXT, opname TEXT, opemail TEXT, opphone TEXT);
			INSERT INTO node VALUES('Ubiquity','PICO2-H EU','5f80ce728aa2032a55e6f86bb3d0dd7b154c5c39','-----BEGIN PUBLIC KEY-----
			MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCtBqXujQ9kefbhpS2sLgu3G6bw
			iwUySFTd10+8X3cVx2OkZnRqqWCRMyjfMhMfRl7duBxcaDb0Q5MhqjsYO7W1y3V+
			Rqu2xn9+HdAYl2EGXD4jwzSiGgMCvtB0vogI+wQVYHVi6X60pu6rfyNWI/4LfVeD
			HAMgIU/cBt7SQ1ESUwIDAQAB
			-----END PUBLIC KEY-----','cc:50:d4:85:86:56:b8:8a:77:57:61:51:63:89:46:09','045894609CCECF9A92533F630DE713A958E96C97CCB8F5ABB5A688A238DEED6DC2D9D0C94EBFB7D526BA6A61764175B99CB6011E2047F9F067293F57F5','-----BEGIN PUBLIC KEY-----
			MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANBUpUcWbR5e8EX5BCdz3pz4D7Xbq5cJ
			6zY9rq94lXoZ2vOijwkAcwrCFzdXDXWETw9/KdO7m6xJa0Yebu7W9zUCAwEAAQ==
			-----END PUBLIC KEY-----','37.810869,-122.267554','Chris Jefferies','operator@gmail.com','510.444.5555');
			CREATE UNIQUE INDEX id ON node(id ASC);
			COMMIT;
			</pre>


			SQLite database definition:
			<pre>
			SQLite format 3ï¿½ï¿½ï¿½@ ï¿½ï¿½ï¿½ï¿½
			ï¿½ï¿½:ï¿½:Ã…Cï¿½ï¿½ï¿½ï¿½ï¿½ï¿½Ã‡itablenodenodeï¿½CREATE TABLE node (model TEXT, version TEXT, id TEXT, rsakeypair TEXT, dsakeypair TEXT, ecdsakeypair TEXT, rootkeypair TEXT, geoloc TEXT, opname TEXT, opemail TEXT, opphone )
			ï¿½
			</pre>

50.0.83.158: /* wlan slovenija */

2013-10-25T05:06:11Z

wlan slovenija

← Older revision		Revision as of 22:06, 24 October 2013
Line 15:		Line 15:
	*node-conf-client: lua client for accepting configs and answering config queries from a configuraion server.		*node-conf-client: lua client for accepting configs and answering config queries from a configuraion server.

	= ~~wlan slovenija~~ =		= Node Attributes =

	~~wlan slovenija has a firmware generator tool. Here~~ are ~~some links~~:		The following attributes are required of the Build Server at image build time:

	*~~[https://github.com/wlanslovenija/nodewatcher/blob/master/generator/config_generator.py config_generator.py: the core code for the generator]~~		*Hardware model
	*~~[https://github.com/wlanslovenija/nodewatcher/blob/master/generator/build_image.py build_image.py: the command line tool that uses config_generator.py]~~		*Firmware version

	~~Some relevant code from config_generator.py~~:		The following attributes are required of the Configuration Server for initial configuration:

	~~<pre>~~		*SSH host RSA keypair
	buildString = 'make image FILES="../files" PROFILE="%s" PACKAGES="policy-routing olsrd uhttpd tc nodewatcher-core nodewatcher-clients ntpclient hostapd -ppp -ppp-mod-pppoe -wpad-mini kmod-l2tp kmod-l2tp-ip kmod-l2tp-eth tunneldigger wireless-tools qos-scripts %s"' % (~~profile_map[self.portLayout], pkgs~~)		*SSH host DSA keypair (optional?)
	~~os.chdir~~(~~path~~)		*SSH host ECDSA keypair (optional?)
	~~os.system(buildString)~~		*SSH keys allowed root access for debugging
	~~</pre>~~

	The ~~whole ''nodewatcher'' system is in fact a web interface to~~ the ~~image generator (this is how it all started, historically, as a web interface + IP allocation, and then we added network monitoring, node telemetry and so on).~~		The following attributes are required of the Node Op for initial configuration through the Configuration Server:

	*~~[http://nodes.wlan-si.net/ live version]~~		*Geographic address
			*Node Op name
			*Node Op email address
			*Node Op phone number

	= freifunk =		= freifunk =

50.0.83.158: /* Node Attributes */

2013-10-25T05:04:58Z

Node Attributes

@@ Line 14: / Line 14: @@
 *node-admin: extended from the openWRT admin page, used by node owner for configuration.
 *node-conf-client: lua client for accepting configs and answering config queries from a configuraion server.
 = wlan slovenija =

Mitar: /* Model (rough) */

2013-10-17T13:09:47Z

Model (rough)

← Older revision		Revision as of 06:09, 17 October 2013
Line 8:		Line 8:
	* python SSL socket server for configuring nodes over secure socket.		* python SSL socket server for configuring nodes over secure socket.
	* python web server as a UI to the SSL configuration server.		* python web server as a UI to the SSL configuration server.
			** SSL libraries on the client (node) are often big. BusyBox wget does not support SSL for example. In wlan slovenija we were thinking of using SSH/SCP instead. [[User:Mitar\|Mitar]] ([[User talk:Mitar\|talk]]) 06:09, 17 October 2013 (PDT)
	SSL libraries on the client (node) are often big. BusyBox wget does not support SSL for example. In wlan slovenija we were thinking of using SSH/SCP instead. [[~~Special~~:~~Contributions/24.5.192.44~~\|~~24.5.192.44~~]] 06:09, 17 October 2013 (PDT)

	Node:		Node:

24.5.192.44: /* Model (rough) */

2013-10-17T13:09:07Z

Model (rough)

← Older revision		Revision as of 06:09, 17 October 2013
Line 8:		Line 8:
	* python SSL socket server for configuring nodes over secure socket.		* python SSL socket server for configuring nodes over secure socket.
	* python web server as a UI to the SSL configuration server.		* python web server as a UI to the SSL configuration server.

			SSL libraries on the client (node) are often big. BusyBox wget does not support SSL for example. In wlan slovenija we were thinking of using SSH/SCP instead. [[Special:Contributions/24.5.192.44\|24.5.192.44]] 06:09, 17 October 2013 (PDT)

	Node:		Node:

Rhodey: /* Model (rough) */

2013-09-26T01:32:06Z

Model (rough)

← Older revision		Revision as of 18:32, 25 September 2013
Line 1:		Line 1:
	= Model (rough) =		= Model (rough) =

	Build Server:		Build Server:
	The one and only server responsible for building and signing SudoMesh OpenWRT images, mostly a collection of bash scripts.		The one and only server responsible for building and signing SudoMesh OpenWRT images, mostly a collection of bash scripts.

	Configuration Server:		Configuration Server:
	One of possibly multiple servers responsible for and authenticated to query, configure and update nodes.		One of possibly multiple servers responsible for and authenticated to query, configure and update nodes.
	* python SSL server for configuring nodes over secure socket.		* python SSL socket server for configuring nodes over secure socket.
	* python web server as a UI to the SSL configuration server.		* python web server as a UI to the SSL configuration server.

	Node:		Node:
	The basic build block of any mesh!		The basic build block of any mesh!
	*node-admin: extended from the openWRT admin page, used by node owner for configuration.		*node-admin: extended from the openWRT admin page, used by node owner for configuration.

Rhodey: /* Node Attributes */

2013-09-26T01:30:53Z

Node Attributes

← Older revision		Revision as of 18:30, 25 September 2013
Line 15:		Line 15:

	= Node Attributes =		= Node Attributes =
	The following attributes are required of the ~~Node Operator for node firmware generation~~:
			The following attributes are required of the Build Server at image build time:

	*Hardware model		*Hardware model
	*~~Primary vs. non-primary AP~~		*Firmware version
	*Geographic address (location)
	*Node Op name
	*Node Op phone number
	*Node Op email address

	The following attributes are ~~to be generated (securely!) on~~ the ~~fly~~ for ~~node firmware generation~~:		The following attributes are required of the Configuration Server for initial configuration:

			*SSH host RSA keypair
	*SSH host DSA keypair (optional?)		*SSH host DSA keypair (optional?)
	*SSH host ECDSA keypair (optional?)		*SSH host ECDSA keypair (optional?)
	*SSH ~~host RSA keypair~~		*SSH keys allowed root access for debugging
	*~~SSH root password~~
			The following attributes are required of the Node Op for initial configuration through the Configuration Server:

			*Geographic address
			*Node Op name
			*Node Op email address
			*Node Op phone number

	= wlan slovenija =		= wlan slovenija =

Rhodey at 01:11, 26 September 2013

2013-09-26T01:11:16Z

← Older revision		Revision as of 18:11, 25 September 2013
Line 1:		Line 1:
			= Model (rough) =

			Build Server:
			The one and only server responsible for building and signing SudoMesh OpenWRT images, mostly a collection of bash scripts.

			Configuration Server:
			One of possibly multiple servers responsible for and authenticated to query, configure and update nodes.
			* python SSL server for configuring nodes over secure socket.
			* python web server as a UI to the SSL configuration server.

			Node:
			The basic build block of any mesh!
			*node-admin: extended from the openWRT admin page, used by node owner for configuration.
			*node-conf-client: lua client for accepting configs and answering config queries from a configuraion server.

	= Node Attributes =		= Node Attributes =
	The following attributes are required of the Node Operator for node firmware generation:		The following attributes are required of the Node Operator for node firmware generation:

50.0.83.158 at 04:43, 23 August 2013

2013-08-23T04:43:29Z

← Older revision		Revision as of 21:43, 22 August 2013
Line 1:		Line 1:
	= Node Attributes =		= Node Attributes =
	The following attributes are required for node firmware generation:		The following attributes are required of the Node Operator for node firmware generation:

	*Hardware model		*Hardware model
Line 8:		Line 8:
	*Node Op phone number		*Node Op phone number
	*Node Op email address		*Node Op email address
	*~~Private~~ SSH ~~key~~
			The following attributes are to be generated (securely!) on the fly for node firmware generation:

			*SSH host DSA keypair (optional?)
			*SSH host ECDSA keypair (optional?)
			*SSH host RSA keypair
			*SSH root password

	= wlan slovenija =		= wlan slovenija =

50.0.83.158 at 03:54, 23 August 2013

2013-08-23T03:54:58Z

← Older revision		Revision as of 20:54, 22 August 2013
Line 1:		Line 1:
			= Node Attributes =
			The following attributes are required for node firmware generation:

			*Hardware model
			*Primary vs. non-primary AP
			*Geographic address (location)
			*Node Op name
			*Node Op phone number
			*Node Op email address
			*Private SSH key

	= wlan slovenija =		= wlan slovenija =