Difference between revisions of "Mesh/Flashing extender nodes"

Jump to navigation Jump to search
no edit summary
Line 146: Line 146:
== Testing and Network Detection ==
== Testing and Network Detection ==


If you flashed
If you flashed your extender node with a dev-build of the firmware, you should now be able to ssh into to it.
change root password
It is probably easiest to first ssh in to your home node over the private interface and then into the extender node with its mesh IP.
 
First, you should immediately change or disable the root password and instead add your ssh key to `/etc/dropbear/authorized_key` (this method of login will not work when sshing through a home node)
   passwd
   passwd


Line 181: Line 183:


There should be a debug message in the log from notdhcpserver concerning the extender node.
There should be a debug message in the log from notdhcpserver concerning the extender node.


== Troubleshooting ==
== Troubleshooting ==


=== USB to Serial Connection ===
=== USB to Serial Connection ===


If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.
If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.
95

edits

Navigation menu