Differences

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

Link to this comparison view

content:meshextender:prototyping_on_mp2 [14/07/2015 17:08]
Nathan Fowler
content:meshextender:prototyping_on_mp2 [14/07/2015 17:31] (current)
Nathan Fowler Added New firmware update Instructions
Line 13: Line 13:
 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=====+======Installing Serval on the WR703N (New way)====== 
 +Perform the following steps on a Linux box, but first ... 
 + 
 +===== SYSADMIN GENERAL'S WARNING ===== 
 + 
 +Because of the inherent risk of human error when instructing the scripts to format and repartition memory sticks, we recommend that you use an old laptop or similar, and dedicate it to this process, so that you do not endanger your data. 
 + 
 +===== WR703N Instructions =====
  - Make sure you have git, csh and expect installed  - Make sure you have git, csh and expect installed
 Depending on your Linux distribution, something like the following should suffice: Depending on your Linux distribution, something like the following should suffice:
Line 100: Line 107:
  
 The WR703N should reboot as a fully functional Mesh Extender. The WR703N should reboot as a fully functional Mesh Extender.
 +===== Configuration=====
 +==== SSH access ====
 +First thing to make sure of is that the noroot  file has been deleted on the USB stick. Once this has been done use
 +<code>
 +$ ssh root@192.168.2.1
 +</code>
 + If this works you should be greeted by a splash screen showing serval version and some other details.\
 +
 +From this you can check if the serval node is functioning properly by using
 +<code>
 +root@192.168.2.1 $ servald status
 +</code>
 +this will return either a few lines saying the status and should contain a line saying whether it is running or it will return a message saying servald is not found. If the latter is what is displayed delete noroot and reboot the mesh node with
 +<code>
 +$ rm /dos/noroot
 +$ reboot
 +</code>
 +The serval node should reboot and work once it has rebooted.
 +
 +====Changing name of the device====
 +This is useful as it allows you to identify specific nodes if a few different ones are within range of each other rather than using sid or the phone number.
 +<code>
 +servald keyring set did `servald id self | tail -1` "Phone number" "Name"
 +</code>
 +This line allows the user to set the phone number and the name of the device for easy identification.
 +
 +====Disabling noroot lockout====
 +WARNING! THIS CAN ALLOW ANYONE ROOT ACCESS IF NECESSARY PRECAUTIONS AREN'T TAKEN WHICH MIGHT INCLUDE CHANGING THE ROOT PASSWORD.
 +
 +ssh into the node using the above method. Once you have access use the following to navigate to the folder which contains the script that produces the noroot file.Then open the script in Vi
 +<code> 
 +$ cd /etc/init.d
 +$vi dropbear
 +</code>
 +
 +Find the two lines in this script that are as follows
 +<code>
 +passwd -l root # lock
 +[ -e /dos/noroot ] && return 1
 +</code>
 +and comment them out by adding a # to the front as follows
 +<code>
 +# passwd -l root # lock
 +# [ -e /dos/noroot ] && return 1
 +</code>
 +
 +Once this has been done you will have root access at all times without having to delete noroot However it is a good idea to change the root password after doing this to discourage unauthorized access. this is achieved by using
 +<code>
 +$ passwd
 +</code>
 +===== Enabling SSH on a Mesh Extender =====
 +
 +Remember if you wish to ssh to the Mesh Extender to power it down, remove the USB memory stick and insert it into any computer, and delete the NOROOT file from the FAT file system partition, and reinsert it into the Mesh Extender.  ssh as root with password root will now be available until next reboot.
 +
 +=====Troubleshooting====
 +====Sysupgrade not found====
 +This means that the openwrt currently on the router cannot find the sysupgrade file
 +  - Download the sysupgrade image for the router you are flashing from this list [[http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/]]
 +  - navigate to the folder where the image is located
 +  - use the following to get the image onto the routers RAM
 +<code>
 +$ scp openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-sysupgrade.bin root@192.168.1.1:/tmp
 +</code
 +  - ssh into the router then use the following command to flash the sysupgrade image
 +<code>
 +# sysupgrade -v /tmp/openwrt-ar71xx-generic-tl-wr703n-v1-squashfs-
 +sysupgrade.bin 
 +</code>
 +  - Follow the serval instructions for your device to reflash serval to the device
 +
 +====Cannot ssh into the device====
 +There can be a few diffferent causes for this issue.
 +===Telnet===
 +This occurs when a root password hasn't been set on the device
 +  - Telnet into the device
 +  - set the root password
 +<code>
 +$ telnet 192.168.1.1
 +# passwd
 +</code>
 +  - after this reboot the device and check if the ssh is working if not try the failsafe route
 +
 +===Failsafe===
 +  - change your computer from DHCP to static ip with an address of 192.168.1.2 and subnet 255.255.255.0
 +  - boot your router into failsafe mode e.g. TP-Link models can be booted into failsafe by holding the reset button once the light starts blinking on boot
 +  - telnet into the router
 +<code>
 +$ telnet 192.168.1.1
 +</code>
 +  - mount the JFSS2 partition to allow you to edit the password or other files that could be causing the issues with
 +<code>
 +# mount_root
 +</code>
 +  - set the passwd if you forgot your password 
 +<code>
 +# passwd
 +</code>
 +  - Reset the router to stock openwrt if issue is not password related by using
 +<code>
 +# firstboot
 +</code>
 +  - Once this is done reboot the router into normal mode using
 +<code>
 +# reboot -f
 +</code>
 +
 +After this you will need to change your network settings back to dhcp to connect to the router through telnet/ssh
  
-===== Installing base OpenWRT on the WR703N =====+====== Installing base OpenWRT on the WR703N ======
  
 WARNING: The following can brick newer WR703Ns (Firmware 1.7, Ver:1.6 or Ver:1.7 etc on the bottom of the unit. Ver:1.2 is known to be safe).  This is an issue with the OpenWRT firmware listed below.  You can safely use these instruction with your own built OpenWRT distro, provided it is new enough. We will do that later. WARNING: The following can brick newer WR703Ns (Firmware 1.7, Ver:1.6 or Ver:1.7 etc on the bottom of the unit. Ver:1.2 is known to be safe).  This is an issue with the OpenWRT firmware listed below.  You can safely use these instruction with your own built OpenWRT distro, provided it is new enough. We will do that later.

Login