76
edits
Difference between revisions of "Mesh/WalkThrough"
Jump to navigation
Jump to search
changed order of configuration
(changed order of configuration) |
|||
| Line 75: | Line 75: | ||
<code>cp settings.js.example settings.js</code> | <code>cp settings.js.example settings.js</code> | ||
The default settings in `settings.js` should suffice in most cases, but if you need to make changes, do them in 'settings.js'. | |||
<code>./makenode.js</code> | <code>./makenode.js</code> | ||
| Line 87: | Line 89: | ||
Now the configuration wizard will ask you a number of questions | Now the configuration wizard will ask you a number of questions:<br> | ||
*"enter valid hostname" - this is the host name when you SSH into the node | *"enter valid hostname" - this is the host name when you SSH into the node - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname] | ||
*"max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network | *"max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobytes per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share. | ||
*"max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. 512 | *"max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps | ||
*"admin user password" - this is the password for for changing wifi settings on the node | *"admin user password" - this is the password for for changing wifi settings on the node | ||
*"root user password" - this is the root password for the router | *"root user password" - this is the root password for the router - Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device - see details below. | ||
*"wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts) | *"wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts) | ||
*"operator name" - this is the name that the network admins can associate with the node - so use a unique name like your first name or location name | *"operator name" - this is the name that the network admins can associate with the node - so use a unique name like your first name or location name | ||
*"private wifi SSID" - this is the wireless SSID name for the private wireless network that will run on this router | *"private wifi SSID" - this is the wireless SSID name for the private wireless network that will run on this router | ||
*"private wifi password" - this is the password for the private wireless network that will run on this router | *"private wifi password" - this is the password for the private wireless network that will run on this router - it must be at least 8 characters long | ||
| Line 110: | Line 112: | ||
It will ask you for a password, which is "meshtheplanet" | It will ask you for a password, which is "meshtheplanet" | ||
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. | |||
==What now?== | ==What now?== | ||