128
edits
Difference between revisions of "Mesh/Technical Overview"
adding ssh instructions
Redconfetti (talk | contribs) (adding ssh instructions) |
|||
| Line 35: | Line 35: | ||
The private network does not limit bandwidth and provides access to both direct access to the Internet (if the node owner has hooked the node up to the Internet) and access to the mesh. Each node's private network runs on 172.30.0.0/16 and uses NAT between the private network and the mesh. It does not accept any new incoming connections from the mesh onto the 172.30.0.0/16 subnet. | The private network does not limit bandwidth and provides access to both direct access to the Internet (if the node owner has hooked the node up to the Internet) and access to the mesh. Each node's private network runs on 172.30.0.0/16 and uses NAT between the private network and the mesh. It does not accept any new incoming connections from the mesh onto the 172.30.0.0/16 subnet. | ||
= Accessing Home Node via SSH = | |||
Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server on port 22. | |||
The 4 Ethernet ports that are provided with your router should be configured as follows: | |||
# Private network with DHCP of 172.30.0.x network addresses | |||
# Public network with DHCP of 100.64.x.x network addresses (SudoMesh network) | |||
# NotDHCP for Extender 1 | |||
# NotDHCP for Extender 2 | |||
This may not apply to your router. For instance, the TP-Link N750 uses the opposite port assignment, with port 3 for private network, and port 4 for public SudoMesh/PeoplesOpen.net network. | |||
== Network Settings == | |||
== 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' after setting up your computer to use an IP on the 172.22.0.0/16 network. | |||
== Post Makenode Configuration == | |||
The private network configuration uses a 172.30.0.0/16 network with DHCP available for connected clients. You can configure your workstation to use the following manual network configuration so that you can SSH into your home node. | |||
* IP Address: 172.30.0.9 (or anything other than 172.30.0.1) | |||
* Netmask: 255.255.255.0 | |||
* Gateway: 172.30.0.1 | |||
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] | |||
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. | |||
== Node flashing and configuration == | == Node flashing and configuration == | ||