User Tools

Site Tools


content:meshextender:prototyping_on_mp2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
content:meshextender:prototyping_on_mp2 [15/02/2013 12:40]
Paul Gardner-Stephen [/etc/config/network]
content:meshextender:prototyping_on_mp2 [14/07/2015 00:38]
Nathan Fowler
Line 12: Line 12:
  
 The TL-WR703N is well supported by OpenWRT: http://wiki.openwrt.org/toh/tp-link/tl-wr703n The TL-WR703N is well supported by OpenWRT: http://wiki.openwrt.org/toh/tp-link/tl-wr703n
 +
 +=====Installing Serval on the WR703N=====
 + - Make sure you have git, csh and expect installed
 +Depending on your Linux distribution, something like the following should suffice:
 +<code>
 +$ sudo yum install csh expect git
 +</code>
 +Alternatively you may need to use
 +<code>
 +$ sudo apt-get install csh expect git
 +</code>
 +  - Download the Mesh Extender Builder software.
 +<code>
 +$ git clone --quiet https://github.com/servalproject/mesh-extender-builder.git 703n-builder
 +</code>
 +  - Allow Edits to the files in the folder
 +<code>
 +$ chmod 777 703n-builder
 +$ cd 703n-builder
 +</code>
 +  - Edit the files that get the openwrt images to get the right images.(make_image, gather-image-files, and flash-virgin-mr3020)
 +make_image
 +<code>
 +# Download and unpack OpenWRT 12.09 image builder (if required).
 +if [ ! -e OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486 ]; then
 +   if [ ! -e OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486.tar.bz2 ]; then
 +      wget http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486.tar.bz2
 +   fi;
 +   tar jxvf OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486.tar.bz2
 +fi;
 +
 +# Build image with all the right packages, and the extra configuration files we need.
 +cd OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486
 +make image PROFILE=TLWR703 "PACKAGES=kmod-lib-crc16 kmod-scsi-core kmod-usb-storage-extras kmod-usb-storage libuuid libblkid libcom_err libpthread libext2fs e2fsprogs kmod-nls-cp437 fdisk kmod-fs-ext4 kmod-fs-vfat kmod-nls-iso8859-1 librt terminfo dosfsck uhttpd lua" FILES=../image-files
 +
 +# Copy build image to here, and show the user
 +cp bin/ar71xx/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin ..
 +cd ..
 +
 +echo "Mesh Extender firmware image built:"
 +ls -l openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin
 +</code>
 +gather-image-files
 +  - change line 71 as follows
 +<code>
 +cp ../openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin .
 +</code>
 +flash-virgin-mr3020
 +  - Change line 12 as follows
 +<code>
 +firmware=openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-factory.bin
 +</code> 
 +- Build the OpenWRT image (this will download a lot of stuff the first time you run it, but you can re-run it quickly there after if you change something).
 +<code>
 +$ ./make_image
 +</code>
 +  - Build the serval.up file
 +<code>
 +$ ./gather-image-files
 +</code>
 +  - Insert the USB memory stick into the installation computer, noting its device name(can be found by typing "df" into the console), then unmount all the device partitions, then partition it using the following script, replacing deviceid with the Linux disk device, e.g., sdf.  MAKE SURE YOU GIVE IT THE RIGHT DEVICE OR IT MIGHT TRY TO REPARTITION YOUR HARD DRIVE!
 +<code>
 +$ umount /dev/deviceid
 +$ ./partition-memory-stick.sh deviceid
 +</code>
 +  - Remove and reinsert the USB memory stick so that the kernel notices the new partition table.
 +  - Unmount the USB partitons again
 +  - Populate the USB memory stick, again replacing deviceid with the right device, e.g., sdf. MAKE SURE YOU GIVE IT THE RIGHT DEVICE OR IT MIGHT ERASE THE PARTITIONS ON YOUR HARD DRIVE!
 +<code>
 +$ ./populate-memory-stick deviceid
 +</code>
 +  - Unplug the USB memory stick and insert it into the MR3020 that is to become a mesh extender.
 +  - Power up the MR3020, and connect it via ethernet to the installation machine, and wait a couple of minutes for it to boot up.
 +  - If the MR3020 is still running the stock firmware, flash it this way:
 +<code>
 +$ ./flash-virgin-mr3020
 +</code>
 +You may need to specify the IP address on the command line if the script doesn't auto-detect the IP address. The most likely address is 192.168.0.254
 +  - If the MR3020 already has OpenWRT, flash it this way.  (You might need to boot the Mesh Extender into fail-safe mode first.)
 +<code>
 +$ ./reflash-mesh-extender
 +</code>
 +You may need to specify the IP address on the command line if the script doesn't auto-detect the IP address. The most likely address is 192.168.1.1 or 192.168.2.1, e.g.:
 +<code>
 +$ ./reflash-mesh-extender 192.168.2.1
 +</code>
 +
 +The WR703N should reboot as a fully functional Mesh Extender.
  
 ===== Installing base OpenWRT on the WR703N ===== ===== Installing base OpenWRT on the WR703N =====
Line 142: Line 230:
  
 Change the IP address in this file from 29.167.164.237 to something random between 28.0.0.0 and 29.255.255.255 Change the IP address in this file from 29.167.164.237 to something random between 28.0.0.0 and 29.255.255.255
 +Change the IP address from 192.168.2.1 to 192.168.2.x if you want to be able to ssh in without ssh complaining about conflicting keys all the time.
  
 <file> <file>
Line 203: Line 292:
 </file> </file>
  
-==== /etc/rc.d/S41servald ====+==== /etc/rc.d/S94servald ====
  
 Don't forget to chmod 755 this file once you have installed it Don't forget to chmod 755 this file once you have installed it
Line 217: Line 306:
   export SERVALINSTANCE_PATH=/etc/serval   export SERVALINSTANCE_PATH=/etc/serval
   mkdir -p $SERVALINSTANCE_PATH   mkdir -p $SERVALINSTANCE_PATH
-  servald start+  /serval/runservald &
 } }
  
Line 226: Line 315:
 </file> </file>
  
 +==== /serval/runservald ====
 +
 +Don't forget to chmod 755 this and the other scripts.
 +
 +<file>
 +#!/bin/sh
 +while [ 1 ]
 +do
 +/serval/servald start foreground
 +done
 +</file>
 ==== /etc/serval/servald.conf ==== ==== /etc/serval/servald.conf ====
 +
 +The small MDP block size is necessary due to the high bit error rate on the radios, and the suboptimal scheduling of rhizome mdp packets (including the lack of supression of duplicate requests).
 +
 +The small max_internal_blob_size is to get around the VERY slow performance of sqlite on the USB memory on the WR703N, which could take several minutes to prepare an empty blob, before even beginning to put any data into it.
 +
 +The long timeout (30seconds) is so that we don't easily drop transfers, especially while the previously mentioned problems persist.
  
 <file> <file>
-rhizome.datastore_path=/serval 
-interfaces.1.type=catear 
-interfaces.1.file=/dev/ttyUSB0 
 interfaces.1.encapsulation=single interfaces.1.encapsulation=single
 +interfaces.1.file=/dev/ttyUSB0   
 interfaces.1.socket_type=stream interfaces.1.socket_type=stream
-interfaces.2.match=eth0+interfaces.1.type=catear        
 +interfaces.2.match=eth0 
 interfaces.2.type=ethernet interfaces.2.type=ethernet
-interfaces.3.type=wifi +interfaces.3.match=wlan0   
-interfaces.3.match=wlan0 +interfaces.3.type=wifi  
-interfaces.4.type=wifi+
 interfaces.4.match=wlan0-1 interfaces.4.match=wlan0-1
 +interfaces.4.type=wifi    
 +rhizome.datastore_path=/serval
 +rhizome.idle_timeout=30000    
 +rhizome.rhizome_mdp_block_size=100
 +rhizome.max_internal_blob_size=16384
 </file> </file>
 ==== /etc/config/dhcp ==== ==== /etc/config/dhcp ====
Line 359: Line 468:
 ====== Configuring RFD900 Radios for use ====== ====== Configuring RFD900 Radios for use ======
  
-Connect as described above and set air speed to 250kbit, and serial speed to 57600, and TX power to +24dBm with a command sequence like:+Connect as described above and set air speed to 128kbit, and serial speed to 57600, and TX power to +24dBm with a command sequence like:
  
 <file> <file>
 ATS1=57 ATS1=57
-ATS2=250+ATS2=128
 ATS4=24 ATS4=24
 ATI5 ATI5
Line 369: Line 478:
 </file> </file>
  
-(We could use 115200, but that would require a recompile of servald, which currently assumes radios at 57600, and the gain would be small, because 250k/2=115kbit total bandwidth, shared among both ends gives 57600 for each end.)+We could use 115200 for the serial speed, but that would require a recompile of servald, which currently assumes radios at 57600, and the gain would be small, because 128k/2=64kbit total bandwidth, shared among both ends gives 32000 for each end, and so it is unlikely that the bandwidth will be depleted. 
 + 
 +128kbit is the fastest effective radio speed until we get some better forward error correction.  250kbit should work, but proved to be quite unreliable, with desynchronisation and high levels of packet loss.
content/meshextender/prototyping_on_mp2.txt · Last modified: 14/07/2015 01:01 by Nathan Fowler