Difference between revisions of "Mesh/Firmware/Overview"

From Sudo Room
Jump to navigation Jump to search
Line 1: Line 1:
= Accessing Home Node via SSH ==
+
= Accessing Home Node via SSH =
  
NOTE: This is a work in progress. These notes are not necessarily accurate.
+
Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server.
  
You should be able to connect to your device via one of the WiFi SSID's detected by your computer. Inspect the network settings assigned to your machine to discover the gateway address, which is the IP address of your home node.
+
== Network Settings ==
  
Once you've obtained this IP address, make sure to write it down. You can use it to SSH into your home node when you are connected to the SudoMesh network. Alternatively you can always connect to the private network port of your home node (port 3) and SSH into the node as root on 172.30.0.1
+
The private network configuration uses the 172.22.0.x network.
  
  ssh root@172.30.0.1
+
Reconfigure your machine to use the following network settings, then connect it to Ethernet port 1 to connect on the local private network interface.
 +
 
 +
* IP Address: 172.22.0.9
 +
* Netmask: 255.255.255.0
 +
* Gateway: 0.0.0.0
 +
 
 +
See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]
 +
 
 +
== Default Build Configuration ==
 +
 
 +
The IP address of your home node is <tt>172.22.0.1</tt> prior to configuration via the [https://github.com/sudomesh/makenode makenode] utility. You can SSH into the node as <tt>root</tt> using the password 'meshtheplanet'.
 +
 
 +
== Post Makenode Configuration ==
 +
 
 +
The IP of your home node on the private network is <tt>172.30.0.1</tt>, with the root password you specified when running <tt>makenode</tt> to configure it.
 +
 
 +
  ssh root@172.30.0.1
 +
  The authenticity of host '172.30.0.1 (172.30.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.
 +
 
 +
== SSH Keys ==
 +
 
 +
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.

Revision as of 21:14, 4 May 2016

Accessing Home Node via SSH

Your home node is accessible via the Dropbear Secure Shell (SSH) server.

Network Settings

The private network configuration uses the 172.22.0.x network.

Reconfigure your machine to use the following network settings, then connect it to Ethernet port 1 to connect on the local private network interface.

  • IP Address: 172.22.0.9
  • Netmask: 255.255.255.0
  • Gateway: 0.0.0.0

See Network Configuration Guides: Linux Mac

Default Build Configuration

The IP address of your home node is 172.22.0.1 prior to configuration via the makenode utility. You can SSH into the node as root using the password 'meshtheplanet'.

Post Makenode Configuration

The IP of your home node on the private network is 172.30.0.1, with the root password you specified when running makenode to configure it.

 ssh root@172.30.0.1
 The authenticity of host '172.30.0.1 (172.30.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.

SSH Keys

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.