Difference between revisions of "Mesh/WalkThrough"

285 bytes added ,  20:49, 4 May 2016
Line 159: Line 159:
=== SSH into your Home Node ===
=== SSH into your Home Node ===


Your home node is now running a Secure Shell (SSH) server. You can run the following command to attempt to log into your home node.
Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server. You can run the following command to attempt to log into your home node.


   ssh root@172.22.0.1
   ssh root@172.22.0.1
  The authenticity of host '172.22.0.1 (172.22.0.1)' can't be established.
  RSA key fingerprint is b8:9d:4a:2f:1b:f5:e1:ae:b8:19:5b:70:92:8b:7f:34.
  Are you sure you want to continue connecting (yes/no)?


After accepting the key by entering 'yes' and pressing ENTER, it will ask you for the root password.  
After accepting the key by entering 'yes' and pressing ENTER, it will ask you for the root password.  


By default the root password used after flashing the device using a SudoMesh firmware build is "meshtheplanet". If you have configured your device already using `./makenode`, you'll need to use the root password you specified.
The default the root password used after flashing your home node with the SudoMesh firmware build is <tt>meshtheplanet</tt>. If you have configured your device already using `./makenode`, you'll need to use the root password you specified.


If you'd like to add your ssh key to the router (instead of using a root password), add it to the `configs/authorized_keys` file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.
If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.


=== Confirm that the Node is Running ===
=== Confirm that the Node is Running ===
128

edits