186
edits
Difference between revisions of "Mesh/Home and extender nodes"
Mesh/Home and extender nodes (view source)
Revision as of 12:46, 7 January 2016
, 12:46, 7 January 2016→Info: Info about home nodes admin and ethernet ports
(→Info: Info about home nodes admin and ethernet ports) |
|||
| Line 24: | Line 24: | ||
== Info == | == Info == | ||
=== Wifi Signals/SSIDs === | |||
Home nodes broadcast 3 SSIDs (these are the wifi names that you can connect to): | Home nodes broadcast 3 SSIDs (these are the wifi names that you can connect to): | ||
* `peoplesopen.net` - the public network that anyone can connect to and that connects to the rest of the mesh | * `peoplesopen.net` - the public network that anyone can connect to and that connects to the rest of the mesh | ||
* `pplsopen.net-node2node` - the "adhoc" network that the node will use to connect to other routers | * `pplsopen.net-node2node` - the "adhoc" network that the node will use to connect to other routers | ||
* (Your private SSID Name) - you can set a private ssid name and a wpa2 password to connect to the node. When you're connected to this network, you won't be connected to the rest of the mesh, and your traffic will not be routed through the mesh exit server. You can connect to this ssid to use the web admin to make basic config changes. | * (Your private SSID Name) - you can set a private ssid name and a wpa2 password to connect to the node. When you're connected to this network, you won't be connected to the rest of the mesh, and your traffic will not be routed through the mesh exit server. You can connect to this ssid to use the web admin to make basic config changes. | ||
=== Admin Access === | |||
Administrative tasks can be done with the web ui. You must be connected to the router via the "private" wifi signal/ssid. When connected over the private network, you can visit http://privatenode.sudomesh.org or http://172.30.0.1 | |||
In that web ui you can change the amount of bandwidth you'd like to share, the private ssid and wpa passwords, and the admin password. | |||
=== Root Login === | |||
When the node is originally configured, it is set with a root password. If you want shell access to the device, you can use this password to login as root. It's sort of generally preferable that you use ssh keys, which are stored on the node in `/etc/dropbear/authorized_keys`. | |||
During alpha testing there will be three developer keys stored there so that our dev volunteers can access the devices for maintenance and diagnostics. If you want to remove access, feel free to comment out those lines, but please keep in mind that this limits our effectiveness to troubleshoot and upgrade during this period. | |||
=== Ethernet Ports === | |||
As of 1/6/2016, home nodes are being configured with 1 WAN (internet port), 2 "peoplesopen.net" ports, and 2 "extender node" ports. | |||
The WAN port will be labeled "internet" and will be a different color than the rest. If you have a home internet connection that you'd like to share, connect this port to your upstream router or cable box from your ISP. | |||
The "peoplesopen.net" ports function as LAN ports on the network. They are assigned a DHCP lease/ip within the peoplesopen.net subnet and can access (and be accessed by) all of the other computers on the mesh. They are functionally equivalent to connecting to the "peoplesopen.net" ssid. | |||
The "extender node" ports are for connecting extender nodes, whose functions are detailed below. The home node will be running a `notdhcpserver` daemon listening on those ports, so if you connect an extender node to them, the two devices **should** automatically negotiate the correct ip address and additional parameters for the extender node. | |||
Unfortunately, the different hardwares have different numbering for the non "internet" ports, so which ports are for extenders and which are "peoplesopen.net lan" ports will not always be the same from device to device. It's fairly easy to test, though. Simply connect a laptop or other computer to one. If it receives a DHCP lease/ip address within the mesh subnet (100.64.0.0/10), then it is a "peoplesopen.net" port. If not, then it is an extender port. | |||
= Extender nodes = | = Extender nodes = | ||