newUI-25
This commit is contained in:
ab7pa
parent
53a6c4d132
commit
9b58a480be
|
|
@ -63,6 +63,7 @@ a. **License grant.**
|
|||
B. produce and reproduce, but not Share, Adapted Material for NonCommercial purposes only.
|
||||
|
||||
2. **Exceptions and Limitations.** For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
|
||||
|
||||
3. **Term.** The term of this Public License is specified in Section 6(a).
|
||||
|
||||
4. **Media and formats; technical modifications allowed.** The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
|
||||
|
|
@ -130,9 +131,9 @@ For the avoidance of doubt, this Section 4 supplements and does not replace Your
|
|||
Section 5 – Disclaimer of Warranties and Limitation of Liability.
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
a. **Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.**
|
||||
a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
|
||||
|
||||
b. **To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.**
|
||||
b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
|
||||
|
||||
|
|
|
|||
|
|
@ -74,36 +74,32 @@ Different TFTP client programs may have different command line options or flags
|
|||
|
||||
Download the appropriate *factory* file for your device by following the instructions in the **Downloading AREDN Firmware** section of this documentation.
|
||||
|
||||
1. Set your computer’s Ethernet network adapter to a static IP address that is a member of the correct subnet for your device. Check the documentation for your specific hardware to determine the correct network number. As in the example below, most Ubiquiti devices have a default IP address of 192.168.1.20, so you can give your computer a static IP on the 192.168.1.x network with a netmask of 255.255.255.0. For example, set your Ethernet adapter to a static IP address of 192.168.1.10.
|
||||
|
||||
You can choose any number for the fourth octet, as long as it is not the same as the IP address of the node. Of course you must also avoid using 192.168.1.0 and 192.168.1.255, which are reserved addresses that identify the network itself and the broadcast address for that network. Other devices may have different default IP addresses or subnets, so select a static IP for your computer which puts it on the same subnet but does not conflict with the default IP of the device.
|
||||
1. Set your computer’s Ethernet network adapter to a static IP address that is a member of the correct subnet for your device. Check the documentation for your specific hardware to determine the correct network number. As in the example below, most Ubiquiti devices have a default IP address of 192.168.1.20, so you can give your computer a static IP on the 192.168.1.x network with a netmask of 255.255.255.0. For example, set your Ethernet adapter to a static IP address of 192.168.1.10. You can choose any number for the fourth octet, as long as it is not the same as the IP address of the node. Of course you must also avoid using 192.168.1.0 and 192.168.1.255, which are reserved addresses that identify the network itself and the broadcast address for that network. Other devices may have different default IP addresses or subnets, so select a static IP for your computer which puts it on the same subnet but does not conflict with the default IP of the device.
|
||||
|
||||
2. Connect an Ethernet cable from your computer to the dumb switch, and another cable from the LAN port of the PoE adapter to the switch.
|
||||
|
||||
3. Put the Ubiquiti device into TFTP mode by holding the reset button while plugging your node's Ethernet cable into the *POE* port on the PoE adapter. Continue holding the device's reset button for approximately 30 to 45 seconds until you see the LEDs on the node alternating in a 1-3, 2-4, 1-3, 2-4 pattern, then release the reset button.
|
||||
|
||||
4. Open a command window on your computer and execute a file transfer command to send the AREDN |trade| firmware to your device. Target the default IP address of your Ubiquiti node, such as 192.168.1.20 (or 192.168.1.1 for AirRouters). The following is one example of TFTP commands that transfer the firmware image to a node:
|
||||
4. Open a command window on your computer and execute a file transfer command to send the AREDN |trade| firmware to your device. Target the default IP address of your Ubiquiti node, such as 192.168.1.20 (or 192.168.1.1 for AirRouters). The TFTP client should indicate that data is being transferred and eventually completes. The following is one example of TFTP commands that transfer the firmware image to a node:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
[Linux/Mac]
|
||||
> tftp 192.168.1.20
|
||||
> bin [Transfer in "binary" mode]
|
||||
> trace on [Show the transfer in progress]
|
||||
> put <full path to the firmware file>
|
||||
[For example, put /tmp/aredn-<release>-factory.bin]
|
||||
-----------------------------------
|
||||
[Windows with command on a single line]
|
||||
> tftp.exe -i 192.168.1.20 put C:\temp\aredn-<release>-factory.bin
|
||||
|
||||
The TFTP client should indicate that data is being transferred and eventually completes.
|
||||
[Linux/Mac]
|
||||
> tftp 192.168.1.20
|
||||
> bin [Transfer in "binary" mode]
|
||||
> trace on [Show the transfer in progress]
|
||||
> put <full path to the firmware file>
|
||||
[For example, put /tmp/aredn-<release>-factory.bin]
|
||||
-----------------------------------
|
||||
[Windows with command on a single line]
|
||||
> tftp.exe -i 192.168.1.20 put C:\temp\aredn-<release>-factory.bin
|
||||
|
||||
5. The node will now automatically reboot with the new AREDN |trade| firmware image.
|
||||
|
||||
Ubiquiti 802.11ac First Install Process
|
||||
---------------------------------------
|
||||
|
||||
.. note:: The install process for these devices requires detailed steps that are best followed using the procedure below, so no separate *Install Checklist* is provided for Ubiquiti 802.11ac devices.
|
||||
.. attention:: The install process for these devices requires detailed steps that are best followed using the procedure below, so no separate *Install Checklist* is provided for Ubiquiti 802.11ac devices.
|
||||
|
||||
Prerequisites
|
||||
The installing computer must be capable of connecting to the command line of the target device. This will require that the computer support both the *ssh* and *scp* protocols. *SSH* and *scp* are native to both Linux and MacOS. The OpenSSH package (which contains both commands) can be enabled on Windows computers. For more information, see the **Preparing Your Computer** section above.
|
||||
|
|
@ -249,9 +245,9 @@ Windows Procedure
|
|||
|
||||
3. Start the *Tiny PXE* server exe and select your computer's Ethernet IP address from the dropdown list called ``Option 54 [DHCP Server]``, making sure to check the ``Bind IP`` checkbox. Under the "Boot File" section, enter ``rb.elf`` into the the *Filename* field, and uncheck the checkbox for "Filename if user-class = gPXE or iPXE". Click the *Online* button at the top of the *Tiny PXE* window.
|
||||
|
||||
.. image:: _images/tiny-pxe-mik.png
|
||||
:alt: Tiny PXE Display for Mikrotik
|
||||
:align: center
|
||||
.. image:: _images/tiny-pxe-mik.png
|
||||
:alt: Tiny PXE Display for Mikrotik
|
||||
:align: center
|
||||
|
||||
4. With the unit powered off, press and hold the reset button on the node while powering on the device. Continue holding the reset button until you see ``TFTPd: DoReadFile: rb.elf`` in the *Tiny PXE* log window.
|
||||
|
||||
|
|
@ -264,26 +260,26 @@ Windows Procedure
|
|||
Install the *sysupgrade* Firmware Image
|
||||
1. After booting the **elf** image the node will have a default IP address of 192.168.1.1. Your computer should already have a static IP address on this subnet, but if not then give your computer an IP address on this subnet.
|
||||
|
||||
.. warning:: For the *Mikrotik hAP ac* family of devices, disconnect the Ethernet cable from the WAN port (1) on the Mikrotik and insert it into one of the LAN ports (2,3,4) before you proceed.
|
||||
.. warning:: For the *Mikrotik hAP ac* family of devices, disconnect the Ethernet cable from the WAN port (1) on the Mikrotik and insert it into one of the LAN ports (2,3,4) before you proceed.
|
||||
|
||||
You should be able to ping the node at 192.168.1.1. Don't proceed until you can ping the node. You may need to disconnect and reconnect your computer's network cable to ensure that your IP address has been reset. Also, you may need to clear your web browser's cache in order to remove cached pages remaining from your node's previous firmware version.
|
||||
2. You should be able to ping the node at 192.168.1.1. Don't proceed until you can ping the node. You may need to disconnect and reconnect your computer's network cable to ensure that your IP address has been reset. Also, you may need to clear your web browser's cache in order to remove cached pages remaining from your node's previous firmware version.
|
||||
|
||||
2. In a web browser, open the node’s Administration page ``http://192.168.1.1/cgi-bin/admin`` (user = 'root', password = 'hsmm') and immediately navigate to the *Firmware Update* section. Browse to find the *sysupgrade* **bin** file you previously downloaded and click the *Upload* button.
|
||||
3. In a web browser, open the node’s Administration page ``http://192.168.1.1/cgi-bin/admin`` (user = 'root', password = 'hsmm') and immediately navigate to the *Firmware Update* section. Browse to find the *sysupgrade* **bin** file you previously downloaded and click the *Upload* button.
|
||||
|
||||
As an alternative to using the node's web interface, you can manually copy the *sysupgrade* **bin** file to the node and run a command line program to install the firmware. This will allow you to see any error messages that may not appear when using the web interface. Note that devices running AREDN |trade| firmware images use port 2222 for secure copy/shell access.
|
||||
As an alternative to using the node's web interface, you can manually copy the *sysupgrade* **bin** file to the node and run a command line program to install the firmware. This will allow you to see any error messages that may not appear when using the web interface. Note that devices running AREDN |trade| firmware images use port 2222 for secure copy/shell access.
|
||||
|
||||
Execute the following commands from a Linux computer:
|
||||
Execute the following commands from a Linux computer:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
my-computer:$ scp -P 2222 <aredn-firmware-filename>.bin root@192.168.1.1:/tmp
|
||||
my-computer:$ ssh -p 2222 root@192.168.1.1
|
||||
~~~~~~~ after logging into the node with ssh ~~~~~~~
|
||||
node:# sysupgrade -n /tmp/<aredn-firmware-filename>.bin
|
||||
my-computer:$ scp -P 2222 <aredn-firmware-filename>.bin root@192.168.1.1:/tmp
|
||||
my-computer:$ ssh -p 2222 root@192.168.1.1
|
||||
~~~~~~~ after logging into the node with ssh ~~~~~~~
|
||||
node:# sysupgrade -n /tmp/<aredn-firmware-filename>.bin
|
||||
|
||||
To transfer the image from a Windows computer you can use a *Secure Copy* program such as *WinSCP*. Then use a terminal program such as *PuTTY* to connect to the node via ssh or telnet in order to run the sysupgrade command shown as the last line above.
|
||||
To transfer the image from a Windows computer you can use a *Secure Copy* program such as *WinSCP*. Then use a terminal program such as *PuTTY* to connect to the node via ssh or telnet in order to run the sysupgrade command shown as the last line above.
|
||||
|
||||
3. The node will now automatically reboot with the new AREDN |trade| firmware image.
|
||||
The node will now automatically reboot with the new AREDN |trade| firmware image.
|
||||
|
||||
TP-LINK First Install Process
|
||||
-----------------------------
|
||||
|
|
@ -306,9 +302,9 @@ Linux Procedure
|
|||
|
||||
3. Open a terminal window to execute the following dnsmasq command with escalated privileges:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
> sudo dnsmasq -i eth0 -u joe --log-dhcp --bootp-dynamic --dhcp-range=192.168.0.110,192.168.0.120 -d -p0 -K --dhcp-boot=recovery.bin --enable-tftp --tftp-root=/tftp/
|
||||
> sudo dnsmasq -i eth0 -u joe --log-dhcp --bootp-dynamic --dhcp-range=192.168.0.110,192.168.0.120 -d -p0 -K --dhcp-boot=recovery.bin --enable-tftp --tftp-root=/tftp/
|
||||
|
||||
4. With the unit powered off, press and hold the reset button on the radio while powering on the device. Continue to hold the reset button until you see output information from the computer window where you ran the dnsmasq command, which should happen after 20-30 seconds. Release the reset button when you see the "sent" message, which indicates success, and you can now <ctrl>-C or end dnsmasq.
|
||||
|
||||
|
|
@ -323,9 +319,9 @@ Windows Procedure
|
|||
|
||||
3. Start the *Tiny PXE* server exe and select your computer's Ethernet IP address from the dropdown list called ``Option 54 [DHCP Server]``, making sure to check the ``Bind IP`` checkbox. Under the "Boot File" section, enter ``recovery.bin`` into the the *Filename* field, and uncheck the checkbox for "Filename if user-class = gPXE or iPXE". Click the *Online* button at the top of the *Tiny PXE* window.
|
||||
|
||||
.. image:: _images/tiny-pxe-tpl.png
|
||||
:alt: Tiny PXE Display for TP_LINK
|
||||
:align: center
|
||||
.. image:: _images/tiny-pxe-tpl.png
|
||||
:alt: Tiny PXE Display for TP_LINK
|
||||
:align: center
|
||||
|
||||
4. With the unit powered off, press and hold the reset button on the node while powering on the device. Continue holding the reset button until you see ``TFTPd: DoReadFile: recovery.bin`` in the *Tiny PXE* log window.
|
||||
|
||||
|
|
@ -340,7 +336,7 @@ Download the *Install Checklist* for GL-iNet devices. These devices allow you to
|
|||
|
||||
After the GL-iNet device is first booted and configured, navigate to the **Upgrade** section and click *Local Upgrade* to select the AREDN |trade| *sysupgrade.bin* file you downloaded for your device.
|
||||
|
||||
.. attention:: Be sure to uncheck the **Keep Settings** checkbox, since GL.iNet settings are incompatible with AREDN |trade| firmware. Also, the AR300M16 devices may have a *boot_dev* switch, so be sure to read the `GL.iNet boot documentation <https://docs.gl-inet.com/router/en/3/specification/gl-ar300m/#control-which-firmware-you-are-booting-into>`_ to select the correct boot mode.
|
||||
.. warning:: Be sure to uncheck the **Keep Settings** checkbox, since GL.iNet settings are incompatible with AREDN |trade| firmware. Also, the AR300M16 devices may have a *boot_dev* switch, so be sure to read the `GL.iNet boot documentation <https://docs.gl-inet.com/router/en/3/specification/gl-ar300m/#control-which-firmware-you-are-booting-into>`_ to select the correct boot mode.
|
||||
|
||||
The node will automatically reboot with the new AREDN |trade| firmware image. If for some reason your GL-iNet device gets into an unusable state, you should be able to recover using the process documented here:
|
||||
`GL-iNet debrick procedure <https://docs.gl-inet.com/en/3/tutorials/debrick/>`_
|
||||
|
|
|
|||
|
|
@ -435,7 +435,7 @@ This option configures the radio to link with other nodes via RF across the mesh
|
|||
Channel
|
||||
Click in the field on the right to select a channel for mesh RF communication. Nodes communicate only with other nodes that use the same channel, channel width, and SSID. You can determine the correct settings by talking with other local node operators to find out which settings are required for joining their networks. The options in this list show the channel number as well as the center frequency of each channel.
|
||||
|
||||
.. warning:: You are responsible for using frequencies, channels, bandwidths, and power levels that comply with your country’s Amateur radio license requirements.
|
||||
.. warning:: **You are responsible for using frequencies, channels, bandwidths, and power levels that comply with your country’s Amateur radio license requirements.**
|
||||
|
||||
Channel Width Setting
|
||||
Click in the field at the right to select from the channel widths supported on your device. Most hardware will support 5 MHz, 10 MHz, or 20 MHz channel widths, but some devices will only support specific channel widths. If the choice of channel width is limited, the device will only show its supported widths in the dropdown list.
|
||||
|
|
|
|||
|
|
@ -25,13 +25,13 @@ Left Nav Bar
|
|||
|
||||
Using the icons on the left side bar you can navigate to various displays.
|
||||
|
||||
|icon3| navigates to this **node status** display.
|
||||
|icon3| navigates to this **node status** display.
|
||||
|
||||
|icon4| navigates to the local mesh status page showing the nodes visible on the local mesh network, as well as any services are provided by those nodes.
|
||||
|icon4| navigates to the local mesh status page showing the nodes visible on the local mesh network, as well as any services are provided by those nodes.
|
||||
|
||||
|icon5| navigates to the *Cloud Mesh* view through the Supernode network (if available).
|
||||
|icon5| navigates to the *Cloud Mesh* view through the Supernode network (if available).
|
||||
|
||||
|icon6| navigates to the world map on the AREDN |trade| website.
|
||||
|icon6| navigates to the world map on the AREDN |trade| website.
|
||||
|
||||
Left Column
|
||||
-----------
|
||||
|
|
|
|||
|
|
@ -72,15 +72,17 @@ However, there is a difference if you are downgrading the firmware on a node whi
|
|||
|
||||
1. Use the `AREDN Firmware Selector <http://downloads.arednmesh.org/afs/www/>`_ to download the previous release's install files. For example, if your Ubiquiti Rocket M5 XW is currently running version ``3.23.4.0``, then download the files required for a First Install from release ``3.22.12.0`` which used *ar71xx* (as shown below).
|
||||
|
||||
.. image:: _images/downgrade.png
|
||||
:alt: Downgrading across target architectures
|
||||
:align: center
|
||||
.. image:: _images/downgrade.png
|
||||
:alt: Downgrading across target architectures
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
2. Review the **Installing AREDN Firmware** documentation and follow the steps for the *First Install* procedure that is appropriate for your node model.
|
||||
|
||||
- For Ubiquiti and TP-LINK models you will be uploading the *FACTORY* firmware.
|
||||
- For Mikrotik models you will boot using the *KERNEL* file (which you rename to *rb.elf*) and then immediately apply the *SYSUPGRADE* firmware image.
|
||||
- For GL.iNet models you will use the `recovery procedure <https://docs.gl-inet.com/en/3/tutorials/debrick/>`_ to upload the *SYSUPGRADE* firmware image.
|
||||
- For Ubiquiti and TP-LINK models you will be uploading the *FACTORY* firmware.
|
||||
- For Mikrotik models you will boot using the *KERNEL* file (which you rename to *rb.elf*) and then immediately apply the *SYSUPGRADE* firmware image.
|
||||
- For GL.iNet models you will use the `recovery procedure <https://docs.gl-inet.com/en/3/tutorials/debrick/>`_ to upload the *SYSUPGRADE* firmware image.
|
||||
|
||||
Another possible way to downgrade firmware between architectures is to enable **Dangerous Upgrade** under the *Advanced Configuration* settings. Setting this to *ON* will disable the normal firmware compatibility checks that are done automatically during the firmware install process. This should allow your node to install a firmware image that uses a legacy architecture.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This How-to will show you a method for generating SSH key pairs on a Windows com
|
|||
|
||||
|
|
||||
|
||||
2. Select the *Generate key pair* menu item or click the *Generate* button and you will be asked to make some random mouse movements. After a short while you get a message asking you to wait while the keys are generated. Once it finishes you now have a new key pair.
|
||||
2. Select the *Generate key pair* menu item or click the *Generate* button and you will be asked to make some random mouse movements. After a short while you get a message asking you to wait while the keys are generated. Once it finishes you now have a new key pair. Give the key pair a suitable comment so that you will remember what the keys are used for. Here we just entered ``testkey@wu2s.com`` for an example. Whatever you enter in the "Key Comment" field must look like an email address with no spaces and the "@" present. Normally this field is used to identify a specific *username@hostname*. You can also password protect the SSH login by providing a passphrase if you desire. Record this passphrase so you will remember it for future use.
|
||||
|
||||
.. image:: _images/02-puttygen.png
|
||||
:alt: Label key pair and create pass phrase
|
||||
|
|
@ -28,8 +28,6 @@ This How-to will show you a method for generating SSH key pairs on a Windows com
|
|||
|
||||
|
|
||||
|
||||
Give the key pair a suitable comment so that you will remember what the keys are used for. Here we just entered ``testkey@wu2s.com`` for an example. Whatever you enter in the "Key Comment" field must look like an email address with no spaces and the "@" present. Normally this field is used to identify a specific *username@hostname*. You can also password protect the SSH login by providing a passphrase if you desire. Record this passphrase so you will remember it for future use.
|
||||
|
||||
3. In PuTTYGen you can save your new keys to separate files for later use. To save the public key to a suitable location, click the *Save Public Key* button and enter a filename with a **.pub** extension. Then click the *Save Private Key* button to save your private key to the same location. Give your private key a **.ppk** file extension. Many people save their keys on a USB flash drive to maintain physical possession of them at all times.
|
||||
|
||||
.. image:: _images/03-puttygen.png
|
||||
|
|
@ -46,27 +44,27 @@ This How-to will show you a method for generating SSH key pairs on a Windows com
|
|||
|
||||
|
|
||||
|
||||
If you saved your public key file by clicking the *Save Public Key* button in PuTTYGen you may notice that it contains a header, footer, and lots of end of line characters. Your AREDN |trade| node will not accept the file with these extra characters. The easiest way to resolve this is to go back to PuTTYGen and highlight/select the entire contents of the text area titled "Public key for pasting into OpenSSH authorized_keys file." Copy this text using the CTRL-C keys on your keyboard.
|
||||
If you saved your public key file by clicking the *Save Public Key* button in PuTTYGen you may notice that it contains a header, footer, and lots of end of line characters. Your AREDN |trade| node will not accept the file with these extra characters. The easiest way to resolve this is to go back to PuTTYGen and highlight/select the entire contents of the text area titled "Public key for pasting into OpenSSH authorized_keys file." Copy this text using the CTRL-C keys on your keyboard.
|
||||
|
||||
.. image:: _images/04b-puttygen.png
|
||||
:alt: Puttygen copy key text
|
||||
:align: center
|
||||
.. image:: _images/04b-puttygen.png
|
||||
:alt: Puttygen copy key text
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
Now go to Notepad++ and paste the copied text into a new window. You should see your public key text on a single line without any header/footer or line termination characters.
|
||||
Now go to Notepad++ and paste the copied text into a new window. You should see your public key text on a single line without any header/footer or line termination characters.
|
||||
|
||||
.. image:: _images/04c-puttygen.png
|
||||
:alt: Puttygen copy key text
|
||||
:align: center
|
||||
.. image:: _images/04c-puttygen.png
|
||||
:alt: Puttygen copy key text
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
Save this Notepad++ window to a suitable filename with the **.pub** file extension.
|
||||
Save this Notepad++ window to a suitable filename with the **.pub** file extension.
|
||||
|
||||
.. image:: _images/04d-puttygen.png
|
||||
:alt: Save the public key
|
||||
:align: center
|
||||
.. image:: _images/04d-puttygen.png
|
||||
:alt: Save the public key
|
||||
:align: center
|
||||
|
||||
|
|
||||
|
||||
|
|
|
|||
|
|
@ -65,13 +65,13 @@ The following steps are required to configure a Supernode.
|
|||
|
||||
#. Login to the rebooted device via *ssh* or *telnet* to get a command line prompt, and then manually type and execute each of these commands:
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
# uci -c /etc/config.mesh add aredn supernode
|
||||
# uci -c /etc/config.mesh set aredn.@supernode[0].enable=1
|
||||
# uci -c /etc/config.mesh commit aredn
|
||||
# /usr/local/bin/node-setup -a mesh
|
||||
# reboot
|
||||
# uci -c /etc/config.mesh add aredn supernode
|
||||
# uci -c /etc/config.mesh set aredn.@supernode[0].enable=1
|
||||
# uci -c /etc/config.mesh commit aredn
|
||||
# /usr/local/bin/node-setup -a mesh
|
||||
# reboot
|
||||
|
||||
Your node should now be functioning as a Supernode. To validate this you can do the following:
|
||||
|
||||
|
|
|
|||
|
|
@ -21,9 +21,9 @@ Single-port mode
|
|||
Multi-port mode
|
||||
Ports can be assigned as needed to be LAN, DtD or WAN links. If your virtual interface is VLAN aware, you can tag VLANs; otherwise the interface should be untagged, which is the recommended setting. In this mode the following ports are automatically assigned:
|
||||
|
||||
- First interface: WAN
|
||||
- Second interface: DtD
|
||||
- Third and beyond: LAN
|
||||
- First interface: WAN
|
||||
- Second interface: DtD
|
||||
- Third and beyond: LAN
|
||||
|
||||
.. note:: The images do not include any *vmtools* but they do contain drivers for the standard QEMU/VMware paravirtualized storage and networking. Using the paravirtualized devices is recommended.
|
||||
|
||||
|
|
@ -45,9 +45,9 @@ VMware Install Process
|
|||
|
||||
For VMware you will need to use QEMU tools or another V2V converter in order to convert the image to ``vmdk`` format. Some example software is listed below:
|
||||
|
||||
- `QEMU for Windows binaries (Unoffical) <https://qemu.weilnetz.de/w64/>`_
|
||||
- `QEMU Official downloads <https://www.qemu.org/download/#windows>`_
|
||||
- `Starwind Converter <https://www.starwindsoftware.com/starwind-v2v-converter>`_
|
||||
- `QEMU for Windows binaries (Unoffical) <https://qemu.weilnetz.de/w64/>`_
|
||||
- `QEMU Official downloads <https://www.qemu.org/download/#windows>`_
|
||||
- `Starwind Converter <https://www.starwindsoftware.com/starwind-v2v-converter>`_
|
||||
|
||||
1. Download the latest firmware image from the AREDN |trade| downloads website.
|
||||
|
||||
|
|
@ -55,15 +55,15 @@ For VMware you will need to use QEMU tools or another V2V converter in order to
|
|||
|
||||
3. Convert the ``.img`` to ``.vmdk`` using your V2V converter of choice. For example, if you are using QEMU, open a terminal/command prompt and on Windows navigate to where QEMU is installed (normally ``c:\Program Files\qemu\``). Run the following command, replacing "aredn.vmdk" and "aredn.img" with the filenames you have chosen.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
qemu-img convert -f raw -O vmdk aredn.img aredn.vmdk
|
||||
qemu-img convert -f raw -O vmdk aredn.img aredn.vmdk
|
||||
|
||||
If you are using Virtualbox, below is the built-in command, replacing "aredn.vmdk" and "aredn.img" with the filenames you have chosen.
|
||||
If you are using Virtualbox, below is the built-in command, replacing "aredn.vmdk" and "aredn.img" with the filenames you have chosen.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
VBoxManage internalcommands createrawvmdk -filename aredn.vmdk -rawdisk aredn.img
|
||||
VBoxManage internalcommands createrawvmdk -filename aredn.vmdk -rawdisk aredn.img
|
||||
|
||||
4. Create the VM/Domain on your server, but *do not assign it a disk*.
|
||||
|
||||
|
|
@ -71,9 +71,9 @@ For VMware you will need to use QEMU tools or another V2V converter in order to
|
|||
|
||||
6. ``ssh`` to the ESXi host, navigate to where the ``.vmdk`` file was uploaded and run the following command to verify/fix any conversion issues. This step helps to identify and fix potential image errors.
|
||||
|
||||
::
|
||||
::
|
||||
|
||||
vmkfstools -i uploaded.vmdk verified.vmdk
|
||||
vmkfstools -i uploaded.vmdk verified.vmdk
|
||||
|
||||
7. Assign the verified ``.vmdk`` disk to the VM.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ Radio Spectrum Characteristics
|
|||
|
||||
AREDN |trade| networks operate in the microwave radio spectrum, and licensed Amateur radio operators have unique access to some of these frequencies. For bands in which Amateur operators share the spectrum, there is more chance for RF interference which may make some frequencies unusable for AREDN |trade| data networking. For best results, select frequencies that are not being heavily used within the coverage area.
|
||||
|
||||
.. attention:: **You are responsible for using frequencies, channels, bandwidths, and power levels that comply with your country's Amateur radio license requirements.**
|
||||
.. warning:: **You are responsible for using frequencies, channels, bandwidths, and power levels that comply with your country's Amateur radio license requirements.**
|
||||
|
||||
Channel Information
|
||||
Each band is divided into channels, each of which consists of a 5 MHz frequency offset identified by the center frequency of the channel and assigned a numerical label. In the example below you can see that a selected channel may use more or less of the frequency range based on the chosen channel width. The wider the channel, the more overlap there will be with adjacent channels. Wide channels have the effect of reducing the number of non-overlapping or non-interfering channels that will be available for use. When selecting channels and widths, be sure to use non-overlapping channels. Devices using channels or channel widths that overlap will interfere with one another and cannot communicate to coordinate the sharing of bandwidth.
|
||||
|
|
@ -15,14 +15,14 @@ Channel Information
|
|||
|
||||
Some or all of the bands shown below are shared with other authorized users. For example, all of the upper channels on the 13 cm band are shared with standard FCC Part 15 :abbr:`WiFi (IEEE 802.11x)` users in the US. The following table shows examples of the Amateur radio bands, frequency ranges, and number of channels that are available for AREDN |trade| networking in the US.
|
||||
|
||||
======= ================= ========
|
||||
Band Frequency Range Channels
|
||||
======= ================= ========
|
||||
5 cm 5650-5925 MHz 54
|
||||
9 cm 3300-3445 MHz 14
|
||||
13 cm 2390-2450 MHz 10
|
||||
33 cm 902-928 MHz 4
|
||||
======= ================= ========
|
||||
======= ================= ========
|
||||
Band Frequency Range Channels
|
||||
======= ================= ========
|
||||
5 cm 5650-5925 MHz 54
|
||||
9 cm 3300-3445 MHz 14
|
||||
13 cm 2390-2450 MHz 10
|
||||
33 cm 902-928 MHz 4
|
||||
======= ================= ========
|
||||
|
||||
The choice of a frequency band for AREDN |trade| networking depends on several different factors, but you can "mix and match" bands in your network design as long as both sides of a radio link use the same band, channel, and channel width.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,4 +20,4 @@ An AREDN |trade| network is able to serve as the transport mechanism for the pre
|
|||
|
||||
A foundational design goal of the AREDN |trade| project is to minimize the technical expertise that is normally required to configure a robust radio network. Devices running AREDN |trade| firmware are in many ways self-configuring so that users without a background in IP networking can easily build or connect to a local RF network. As mentioned in a recent `Amateur Radio Digital Communications (ARDC) <https://www.ardc.net/>`_ annual report, "AREDN |trade| software allows volunteers to set up a node with minimal expertise and effort, and because the software configures the network automatically, advanced network technology is not needed."
|
||||
|
||||
This facilitates the primary goal of the AREDN |trade| project, which is **to empower licensed amateur radio operators to quickly and easily deploy high-speed data networks when and where they are needed, as a service both to the hobby and the community.** This is especially important in cases when traditional "utility" services (electricity, phone lines, or Internet services) become unavailable. In those cases an off-grid amateur radio emergency data network may be a lifeline for communities impacted by a local disaster.
|
||||
This facilitates the primary goal of the AREDN |trade| project, which is to empower licensed amateur radio operators to quickly and easily deploy high-speed data networks when and where they are needed, as a service both to the hobby and the community. This is especially important in cases when traditional "utility" services (electricity, phone lines, or Internet services) become unavailable. In those cases an off-grid amateur radio emergency data network may be a lifeline for communities impacted by a local disaster.
|
||||
|
|
|
|||
9
conf.py
9
conf.py
|
|
@ -15,7 +15,7 @@
|
|||
# import os
|
||||
# import sys
|
||||
# sys.path.insert(0, os.path.abspath('.'))
|
||||
import sphinx_rtd_theme
|
||||
###import sphinx_rtd_theme
|
||||
from datetime import date
|
||||
|
||||
# -- Project information -----------------------------------------------------
|
||||
|
|
@ -87,7 +87,8 @@ pygments_style = 'sphinx'
|
|||
# The theme to use for HTML and HTML Help pages. See the documentation for
|
||||
# a list of builtin themes.
|
||||
#
|
||||
html_theme = 'sphinx_rtd_theme'
|
||||
###html_theme = 'sphinx_rtd_theme'
|
||||
html_theme = 'sphinx_book_theme'
|
||||
|
||||
# Theme options are theme-specific and customize the look and feel of a theme
|
||||
# further. For a list of options available for each theme, see the
|
||||
|
|
@ -96,7 +97,9 @@ html_theme = 'sphinx_rtd_theme'
|
|||
html_logo = "_images/AREDN-Logo.png"
|
||||
html_theme_options = {
|
||||
'logo_only': True,
|
||||
'display_version': False,
|
||||
"toc_title": "Page Navigation",
|
||||
"use_download_button": False,
|
||||
### 'display_version': False,
|
||||
}
|
||||
|
||||
# Add any paths that contain custom static files (such as style sheets) here,
|
||||
|
|
|
|||
|
|
@ -75,13 +75,13 @@ If you would like to see the documentation for a specific AREDN |trade| release,
|
|||
arednHow-toGuides/firmware_tips
|
||||
arednHow-toGuides/home-router-connection
|
||||
arednHow-toGuides/poe
|
||||
arednHow-toGuides/lqm
|
||||
arednHow-toGuides/supernodes
|
||||
arednHow-toGuides/command-line
|
||||
arednHow-toGuides/siso-mimo
|
||||
arednHow-toGuides/radio_mobile_settings
|
||||
arednHow-toGuides/dish-aiming
|
||||
arednHow-toGuides/lqm
|
||||
arednHow-toGuides/puttygen_ssh_keys
|
||||
arednHow-toGuides/radio_mobile_settings
|
||||
arednHow-toGuides/siso-mimo
|
||||
arednHow-toGuides/supernodes
|
||||
arednHow-toGuides/local-software-source
|
||||
arednHow-toGuides/xlinks
|
||||
arednHow-toGuides/vm-install
|
||||
|
|
|
|||
Loading…
Reference in New Issue