John's research - Revision history

Ajay at 08:04, 11 June 2009

2009-06-11T08:04:18Z

← Older revision		Revision as of 10:04, 11 June 2009
Line 1:		Line 1:
	[[Category: Development Team Research Pages]]		[[Category: Development Team Research Pages]]

	This page has moved to ~~http://~~wirelessdev~~.meraka.org.za/index.php/John's_research~~		This page has moved to wirelessdev

Jhay: This page has moved to wirelessdev

2009-06-08T17:23:33Z

This page has moved to wirelessdev

Show changes

Jhay: /* Less commonly used/needed configs */

2009-05-20T10:28:59Z

Less commonly used/needed configs

← Older revision		Revision as of 12:28, 20 May 2009
Line 84:		Line 84:
	If you need to override everything for an interface:		If you need to override everything for an interface:
	ifconfig_ath0="mode 11a mediaopt adhoc channel 165 ssid ptabb"		ifconfig_ath0="mode 11a mediaopt adhoc channel 165 ssid ptabb"
			You can also just override the channel with:
			mesh_bbchana="140"
			mesh_bbchanb="140"
			mesh_hspchan="13"

	A specific prefix for an interface:		A specific prefix for an interface:
Line 90:		Line 94:
	If you need to override the ipv4 address:		If you need to override the ipv4 address:
	ipv4_addrs_npe0="10.3.2.1/24"		ipv4_addrs_npe0="10.3.2.1/24"

			If you need to turn 4over6 off or change the prefix:
			auto4over6_enable="NO"
			auto4over6_prefix="fec0:0:0:aaaa::"

			If you need to turn auto updates off or change the extension:
			autoupgrade_enable="NO"
			autoupgrade_url="ftp://mesh-updates/"
			autoupgrade_suffix=".mesh"

	Common files that also might need to be tweaked are:		Common files that also might need to be tweaked are:
	/conf/default/usr.local.etc/olsrd.conf		/conf/default/usr.local.etc/olsrd.conf
	/conf/default/usr.local.etc/dnsmasq.conf		/conf/default/usr.local.etc/dnsmasq.conf

			site_type="auto\|host\|node\|repeater\|hotspot\|quad"
			rtadvd_enable="YES\|NO"
			olsrd_enable="YES\|NO"

	Although, if you need to, tell me so that we can see if it can be handled automagically by a script.		Although, if you need to, tell me so that we can see if it can be handled automagically by a script.

Jhay: /* What is there to tweak */ Start to flesh out our new stuff

2009-05-20T10:13:50Z

What is there to tweak: Start to flesh out our new stuff

← Older revision		Revision as of 12:13, 20 May 2009
Line 57:		Line 57:
	mount -u -r /		mount -u -r /

	A network needs one box that is the dns server. On that box you will need to set		=== Commonly used configs ===

			If the box is the one that connect the network to the "internet", you will have to set
			mesh_type="gateway"
			This will enable a lot of things as listed on the [[High_performance_node_page#Behavior_of_the_GateWay_node_in_a_mesh \| HPN page]], for instance announce a default route, be a dns server for the network, be a ntp time server, be an update server, etc.

			A network needs one box that is the dns server. If you go not have a gateway, you can use this. On that box you will need to set
	mesh_dns_enable="YES"		mesh_dns_enable="YES"

	One thing that is often needed is to swap channels on the BackBone links. ~~You~~ can ~~change~~ it with lines like this:		If you want to give the box a name:
			hostname="ajay-rtr.cids.org.za"

			One thing that is often needed is to swap channels on the BackBone links. On the newer distros, you can configure the box as "green" (default) or "red".
			mesh_node="red"

			On older boxes, you will have to do it with lines like this:
	mesh_bbchana="140"		mesh_bbchana="140"
	mesh_bbchanb="136"		mesh_bbchanb="136"

	~~If you want~~ to ~~give~~ the ~~box a name~~:		To force the box to hunt for channels on the next boot:
	~~hostname~~="~~ajay-rtr.cids.org.za~~"		mesh_hunt="YES"


			=== Less commonly used/needed configs ===

	If you need to override everything for an interface:		If you need to override everything for an interface:

Jhay: /* Todo */

2009-05-20T03:47:06Z

Todo

← Older revision		Revision as of 05:47, 20 May 2009
Line 217:		Line 217:
	* A wacky idea for updating even in the face of incompatible routing protocols. Have every box run a tcp relay to an update box. So every box can connect to a neighbor's relay for updates. This will not solve the problem of incompatible links, eg. adding wep or changing ssids.		* A wacky idea for updating even in the face of incompatible routing protocols. Have every box run a tcp relay to an update box. So every box can connect to a neighbor's relay for updates. This will not solve the problem of incompatible links, eg. adding wep or changing ssids.
	* Robust addressing scheme for big networks that need to cooperate.		* Robust addressing scheme for big networks that need to cooperate.
			* What else?

Jhay: /* Todo */ Add something

2009-03-13T06:22:40Z

Todo: Add something

← Older revision		Revision as of 08:22, 13 March 2009
Line 216:		Line 216:
	* Should updates be signed so that the auto update will only update to a signed distro file?		* Should updates be signed so that the auto update will only update to a signed distro file?
	* A wacky idea for updating even in the face of incompatible routing protocols. Have every box run a tcp relay to an update box. So every box can connect to a neighbor's relay for updates. This will not solve the problem of incompatible links, eg. adding wep or changing ssids.		* A wacky idea for updating even in the face of incompatible routing protocols. Have every box run a tcp relay to an update box. So every box can connect to a neighbor's relay for updates. This will not solve the problem of incompatible links, eg. adding wep or changing ssids.
			* Robust addressing scheme for big networks that need to cooperate.

Jhay: /* Upgrades and Automagic upgrades */ Still need lots of work

2008-08-14T20:04:39Z

Upgrades and Automagic upgrades: Still need lots of work

← Older revision		Revision as of 22:04, 14 August 2008
Line 83:		Line 83:
	==How bits and pieces work==		==How bits and pieces work==
	===Upgrades and Automagic upgrades===		===Upgrades and Automagic upgrades===

			Disk split in 2 partitions. Upgrade the one that is not active.

			Auto script run from cron to check for updates.

			/upgrade tool used for manual updates and by the auto script to do the actual updating.

	===4over6 Automatic tunnels===		===4over6 Automatic tunnels===
	An idea to tunnel IPv4 packets over our IPv6 mesh networks without having to configure each tunnel. Think of it as a kind of one to many tunnel. So only one need to be configured on a host.		An idea to tunnel IPv4 packets over our IPv6 mesh networks without having to configure each tunnel. Think of it as a kind of one to many tunnel. So only one need to be configured on a host.

Jhay: /* What is there to tweak */ Add the requirement to remount /

2008-08-14T06:02:34Z

What is there to tweak: Add the requirement to remount /

← Older revision		Revision as of 08:02, 14 August 2008
Line 52:		Line 52:
	In theory we want to end up tweaking / configuring nothing, but we are not there yet. :-)		In theory we want to end up tweaking / configuring nothing, but we are not there yet. :-)

	These configs go in /conf/default/etc/rc.conf.local unless otherwise specified. You can look in rc.conf.mesh to see what the defaults are, but do not change it there. That will break upgrades.		These configs go in /conf/default/etc/rc.conf.local unless otherwise specified. You can look in rc.conf.mesh to see what the defaults are, but do not change it there. That will break upgrades. Remember that the CF is normally read-only, so has to be made read-write before editing the file with
			mount -u -w /
			And made read-only again afterwards with
			mount -u -r /

	A network needs one box that is the dns server. On that box you will need to set		A network needs one box that is the dns server. On that box you will need to set

Jhay: /* 4over6 Automatic tunnels */ First stab at it

2008-08-14T05:59:47Z

4over6 Automatic tunnels: First stab at it

@@ Line 81: / Line 81: @@
 ===Upgrades and Automagic upgrades===
 ===4over6 Automatic tunnels===
 ==Installing FreeBSD on a Avila/Pronghorn Metro ARM board==

Jhay: /* New Install */ tweak case

2008-08-14T05:50:58Z

New Install: tweak case

← Older revision		Revision as of 07:50, 14 August 2008
Line 142:		Line 142:
	===New Install===		===New Install===
	This is a bit more involved.		This is a bit more involved.
	* For the ~~Arm~~ boards, you will need a tftp server loaded with boot2 and ~~a Arm~~ kernel with nfs booting compiled in. You will also need a		* For the ARM boards, you will need a tftp server loaded with boot2 and an ARM kernel with nfs booting compiled in. You will also need a nfs server setup with an extracted FreeBSD ARM tree.
	nfs server setup with an extracted FreeBSD ~~Arm~~ tree.
	* For the i386 based boards, you will need a dhcp server that can handle PXE (for the soekris), with a tftp server and a nfs server.		* For the i386 based boards, you will need a dhcp server that can handle PXE (for the soekris), with a tftp server and a nfs server.