Clarify Install Steps
Clarify wording on Install Steps based on experiences with latest TP-Link PharOS.
This commit is contained in:
Steve Lewis AB7PA
Joe AE6XE
parent
57ae63c2ab
commit
6e52822f7b
|
|
@ -2,23 +2,19 @@
|
|||
Installing AREDN |trade| Firmware
|
||||
=================================
|
||||
|
||||
The steps for installing device firmware are documented on the AREDN |trade| website in the `Current Software <https://www.arednmesh.org/content/current-software>`_ section. Under the **Software** menu, select **Download** to reach the *Current Software* page.
|
||||
|
||||
There are two cases for installing AREDN |trade| firmware:
|
||||
|
||||
1. If you already have an existing version of AREDN |trade| running on your device, then you can use your computer's web interface to navigate to **Setup > Administration > Firmware Update** to install your new firmware. This process will be explained in more detail in the **Advanced Configuration** section of this guide. Also, see *Firmware Upgrade Tips* in the **How-to Guides** section for additional information.
|
||||
|
||||
----------
|
||||
|
||||
2. If you are installing AREDN |trade| firmware on a device for the first time, each hardware platform may require a unique procedure.
|
||||
|
||||
.. image:: _images/firmware-install.png
|
||||
:alt: Firmware Install Connections
|
||||
:align: center
|
||||
.. image:: _images/firmware-install.png
|
||||
:alt: Firmware Install Connections
|
||||
:align: center
|
||||
|
||||
The diagram above shows that your computer with the downloaded firmware image must be connected to the node using Ethernet cables in order to install the AREDN |trade| image. It is helpful to connect the computer and node through a simple Ethernet switch so that the switch can maintain the computer's link while the node is being rebooted.
|
||||
The diagram above shows that your computer with the downloaded firmware image must be connected to the node using Ethernet cables in order to install the AREDN |trade| image. It is helpful to connect the computer and node through a simple Ethernet switch so that the switch can maintain the computer's network link while the node is being rebooted.
|
||||
|
||||
Different node hardware will require different methods for installing the AREDN |trade| firmware. For Ubiquiti devices, your computer's TFTP client will connect to the node's TFTP server in order to upload the firmware image. For TP-LINK and GL-iNET devices, your computer's web browser will connect to the node's web server to upload the firmware image. For Mikrotik devices, your computer will run a remote boot server and the node's remote boot client will load its boot image from your computer. Refer to the specific procedures below for your node hardware.
|
||||
Different node hardware will require different methods for installing the AREDN |trade| firmware. For **Ubiquiti** devices, your computer's TFTP client will connect to the node's TFTP server in order to upload the firmware image. For **Mikrotik** and **TP-LINK** devices, your computer will run a remote boot server and the node's remote boot client will load its boot image from your computer. For **GL-iNet** devices, your computer's web browser will connect to the node's web server to upload the firmware image. Refer to the specific procedures below for your node hardware.
|
||||
|
||||
Troubleshooting Tips
|
||||
--------------------
|
||||
|
|
@ -26,7 +22,7 @@ Troubleshooting Tips
|
|||
Questions and troubleshooting assistance can usually be obtained by creating a post on the AREDN |trade| `online forum <https://www.arednmesh.org/forum>`_, which has an active community of helpful and experienced operators.
|
||||
|
||||
Browser cache and sessions
|
||||
One common issue can occur when installing firmware using a web browser interface. The browser cache stores data for the URLs that have been visited, but IP addresses and other parameters often change during the install process. It is possible for the cache to contain information that doesn’t match the latest settings for the URL, so the browser may block the connection setup and display an ERR_CONNECTION_RESET message. Clearing the web browser's cache will allow the latest URL settings to be registered so you can continue with the install process.
|
||||
One common issue can occur when installing firmware using a web browser interface. Your computer's web browser cache stores data for the URLs that have been visited, but IP addresses and other parameters often change during the install process. It is possible for the cache to contain information that doesn’t match the latest settings for the URL, so the browser may block the connection setup and display an ERR_CONNECTION_RESET message. Clearing your computer's web browser cache will allow the latest URL settings to be registered so you can continue with the install process.
|
||||
|
||||
Instead of a *Connection Reset* message, sometimes a *Bad Gateway* message may appear. This is an `HTTP Status Code <https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml>`_ that can mean any of several things. Often it indicates a network communication issue between a web browser and a web server. During AREDN |trade| firmware installs you can usually resolve a *Bad Gateway* issue by doing one or more of the following things:
|
||||
|
||||
|
|
@ -36,16 +32,8 @@ Browser cache and sessions
|
|||
* Use a different web browser program or a *Safe Mode / Incognito* browser window.
|
||||
* Unplug and reconnect the Ethernet cable from your computer to ensure that your machine has received a new DHCP IP address on the same subnet as the node's updated IP.
|
||||
|
||||
If for some reason the node's web interface does not work, you may be able to use a command line program to install the firmware image. You must first copy the firmware *bin* file to the node, then log into the node and use the *sysupgrade* program to install the image as illustrated below.
|
||||
|
||||
>>>
|
||||
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 as root (hsmm) ~~~~~~~
|
||||
node:# sysupgrade -n /tmp/aredn-firmware-filename.bin
|
||||
|
||||
Tiny PXE Server
|
||||
On Windows, make sure to allow Tiny PXE Server (described below) through the firewall when prompted on first launch. If you do not get prompted or Tiny PXE Server does not display any activity when you put your device in recovery mode, get to the firewall settings from the Windows control panel and click on *Advanced Settings*. Look through the "Inbound Rules" to see if a rule exists for Tiny PXE Server. If a rule exists, make sure to "allow connection" for both private and public networks. If no rule exists, create a new rule allowing connection for both public and private networks.
|
||||
PXE Server
|
||||
If you are using a TFTP/Bootp server (described below) on a Windows computer, be sure to allow the Tiny PXE server through the Windows firewall when prompted on first launch. If you are not prompted or the Tiny PXE server does not display any activity when you put your device in recovery mode, go to the firewall settings from the Windows control panel and click *Advanced Settings*. Look through the "Inbound Rules" to see if a rule exists for Tiny PXE server. If a rule exists, make sure to "allow connection" for both private and public networks. If no rule exists, create a new rule allowing connection for both public and private networks.
|
||||
|
||||
Ubiquiti First Install Process
|
||||
------------------------------
|
||||
|
|
@ -89,17 +77,88 @@ Download the appropriate *factory* file for your device by following the instruc
|
|||
|
||||
9. Navigate to the *Setup* page and configure the new “firstboot” node as described in the **Basic Radio Setup** section.
|
||||
|
||||
Mikrotik First Install Process
|
||||
------------------------------
|
||||
|
||||
Mikrotik devices require a **two-part install** process: First, install and boot the correct mikrotik-vmlinux-initramfs file with the **elf** extension, and then use this temporary AREDN |trade| Administration display to complete the installation of the appropriate mikrotik-rb file with the **bin** extension.
|
||||
|
||||
Mikrotik devices have a built-in :abbr:`TFTP (Trivial File Transfer Protocol)` and `Bootp <https://en.wikipedia.org/wiki/Bootstrap_Protocol>`_ client which allows them to obtain new firmware from an external source. Your computer must run a TFTP/Bootp *server* (described below) in order to provide firmware images to Mikrotik devices.
|
||||
|
||||
Preparation
|
||||
1. Download the appropriate Mikrotik **elf** and **bin** files. Rename the *elf* file to ``rb.elf`` and keep the *bin* file available for later.
|
||||
|
||||
2. 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 Mikrotik devices use the 192.168.1.x subnet by default, so you can give your computer a static IP such as 192.168.1.100 with a netmask of 255.255.255.0.
|
||||
|
||||
You can choose any number for the fourth octet, as long as it is not the same as the IP address of the node and is not within the range of DHCP addresses you will be providing in step 2 below. 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 use different default subnets, such as QRT units which use 192.168.88.x. Select a static IP for your computer which puts it on the same subnet as your device.
|
||||
|
||||
3. 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. If you are flashing a Mikrotik hAP ac lite device, connect the Ethernet cable from *Port 1* of the Mikrotik to the dumb switch.
|
||||
|
||||
Linux Procedure
|
||||
1. Create a directory on your computer called ``/tftp`` and copy the ``rb.elf`` file there.
|
||||
|
||||
2. Determine your computer’s Ethernet interface name with ``ifconfig``. It will be the interface you set to 192.168.1.100 above. You will use this interface name in the command below as the name after ``-i`` and you must substitute your login user name after ``-u`` below. Use a ``dhcp-range`` of IP addresses that are also on the same subnet as the computer: for example 192.168.1.110,192.168.1.120 as shown below.
|
||||
|
||||
3. Become ``root`` and open a terminal window to execute the following dnsmasq command:
|
||||
|
||||
>>>
|
||||
(root)# dnsmasq -i eth0 -u joe --log-dhcp --bootp-dynamic \
|
||||
--dhcp-range=192.168.1.110,192.168.1.120 -d -p0 -K \
|
||||
--dhcp-boot=rb.elf --enable-tftp --tftp-root=/tftp/
|
||||
|
||||
4. With the PoE unit powered off, connect the Mikrotik node to the POE port. If you are flashing a Mikrotik *hAP ac lite* device, connect the LAN cable from *Port 1* of the Mikrotik to the dumb switch. Press and hold the reset button on the Mikrotik while powering on the device.
|
||||
|
||||
5. 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 about ten seconds. Release the reset button as the computer starts communicating with the node. When you see the "sent" message, this indicates success, and the node has downloaded the image and will reboot. You can now <ctrl>-C or kill dnsmasq.
|
||||
|
||||
Windows Procedure
|
||||
You will need `Tiny PXE <http://reboot.pro/files/file/303-tiny-pxe-server/>`_ software on your Windows computer. Download this software and extract it on your computer.
|
||||
|
||||
1. Navigate to the folder where you extracted the *Tiny PXE* software and edit the ``config.ini`` file. Directly under the ``[dhcp]`` tag, add the following line: ``rfc951=1`` then save and close the file.
|
||||
|
||||
2. Copy the ``rb.elf`` file into the ``files`` folder under the Tiny PXE server directory location.
|
||||
|
||||
3. Start the Tiny PXE server exe and select your Ethernet interface IP 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
|
||||
|
||||
4. With the PoE unit powered off, connect the Mikrotik node to the POE port. If you are flashing a Mikrotik *hAP ac lite* device, connect the LAN cable from *Port 1* of the Mikrotik to the dumb switch.
|
||||
|
||||
5. Press and hold the reset button on the node while powering on the PoE unit or the device. Continue holding the reset button until you see ``TFTPd: DoReadFile: rb.elf`` in the Tiny PXE log window.
|
||||
|
||||
6. Release the node’s reset button and click the *Offline* button in Tiny PXE. You are finished using Tiny PXE when the firmware image has been read by the node.
|
||||
|
||||
Final Configuration Steps
|
||||
1. After booting the AREDN firmware image the node should have a default IP address of 192.168.1.1. Change your computer’s Ethernet interface to DHCP mode to obtain an IP address from the node.
|
||||
|
||||
.. attention:: For the *Mikrotik hAP ac lite* **only**, pull 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. In a web browser, open the node’s Administration page ``http://192.168.1.1/cgi-bin/admin`` (user = 'root', password = 'hsmm') and navigate to the *Setup > Administration > Firmware Update* section. Select the **bin** file you previously downloaded and click the *Upload* button. After uploading the **bin** file, the node will automatically reboot.
|
||||
|
||||
As an alternative to using the node's web interface, you can manually copy the **bin** file to the node and run a command line program to install the image. This will allow you to see any error messages that may not appear when using the web interface. Note that AREDN |trade| nodes use port 2222 for secure copy/shell access.
|
||||
|
||||
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
|
||||
|
||||
To transfer the image from a Windows computer you can use a *Secure Copy* program such as `WinSCP <https://winscp.net>`_. Then use a terminal program such as `PuTTY <https://www.chiark.greenend.org.uk/~sgtatham/putty/>`_ to connect to the node via ssh or telnet in order to run the sysupgrade command shown as the last line above.
|
||||
|
||||
3. After the node reboots, navigate to the node’s *Setup* page and configure the new “firstboot” node as described in the **Basic Radio Setup** section.
|
||||
|
||||
TP-LINK First Install Process
|
||||
-----------------------------
|
||||
|
||||
Preferred Process
|
||||
**TP-LINK** devices currently allow you to use the manufacturer's pre-installed *PharOS* web browser user interface to upload and apply new firmware images. This is the most user-friendly way to install AREDN |trade| firmware. Navigate to the *Setup* section to select and upload new firmware. Check the TP-LINK documentation for your device if you have questions about using their built-in user interface.
|
||||
**TP-LINK** devices may or may not allow you to use the manufacturer's pre-installed *PharOS* web browser interface to apply new firmware images. If available, this is the most user-friendly way to install AREDN |trade| firmware. Navigate to the system setup menu to select and upload new firmware. Check the TP-LINK documentation for your device if you have questions about using their built-in user interface. If this process works then you will have AREDN |trade| firmware installed on your device and you do not need to follow any of the steps described below.
|
||||
|
||||
Alternate Process
|
||||
TP-LINK devices also have a built-in :abbr:`TFTP (Trivial File Transfer Protocol)` and `Bootp <https://en.wikipedia.org/wiki/Bootstrap_Protocol>`_ client which allows them to obtain new firmware from an external source. Your computer must run a TFTP/Bootp server in order to provide firmware images to the node. In certain situations you may need to use this method to update the firmware or to restore a TP-LINK recovery file by following the steps below.
|
||||
|
||||
*Preparation*
|
||||
If the process above does not work or if you choose not to use the *PharOS* web interface, then you can always install AREDN |trade| firmware on your device using the following steps. TP-LINK devices have a built-in :abbr:`TFTP (Trivial File Transfer Protocol)` and `Bootp <https://en.wikipedia.org/wiki/Bootstrap_Protocol>`_ client which allows them to obtain new firmware from an external source. Your computer must run a TFTP/Bootp *server* (described below) in order to provide firmware images to the device.
|
||||
|
||||
Preparation
|
||||
1. Download the appropriate TP-LINK *factory* file and rename this file as ``recovery.bin``
|
||||
|
||||
2. 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 TP-LINK devices use the 192.168.0.x subnet by default, so you can give your computer a static IP such as 192.168.0.100 with a netmask of 255.255.255.0.
|
||||
|
|
@ -108,25 +167,23 @@ Alternate Process
|
|||
|
||||
3. 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.
|
||||
|
||||
*Linux Procedure*
|
||||
|
||||
Linux Procedure
|
||||
1. Create a directory on your computer called ``/tftp`` and copy the TP-LINK ``recovery.bin`` file there.
|
||||
|
||||
2. Determine your computer’s Ethernet interface name with ``ifconfig``. It will be the interface you set to 192.168.0.100 above. You will use this interface name in the command below as the name after ``-i`` and you must substitute your login user name after ``-u`` below. Use a ``dhcp-range`` of IP addresses that are also on the same subnet as the computer: for example 192.168.0.110,192.168.0.120 as shown below.
|
||||
|
||||
3. Become ``root`` and open a terminal window to execute the following dnsmasq command:
|
||||
|
||||
>>>
|
||||
(root)# dnsmasq -i eth0 -u joe --log-dhcp --bootp-dynamic \
|
||||
>>>
|
||||
(root)# 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 PoE unit powered off, connect an Ethernet cable from the TP-LINK node to the POE port.
|
||||
|
||||
5. Push the reset button on the TP-LINK and hold it while powering on the PoE unit. 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 about 10 seconds. Release the reset button as the computer starts communicating with the node. When you see the "sent" message, this indicates success, and the TP-LINK node has downloaded the image and will reboot. You can now <ctrl>C or kill dnsmasq.
|
||||
|
||||
*Windows Procedure*
|
||||
5. Push the reset button on the TP-LINK and hold it while powering on the PoE unit. 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 about 10 seconds. Release the reset button as the computer starts communicating with the node. When you see the "sent" message, this indicates success, and the TP-LINK node has downloaded the image and will reboot. You can now <ctrl>-C or kill dnsmasq.
|
||||
|
||||
Windows Procedure
|
||||
You will need `Tiny PXE <http://reboot.pro/files/file/303-tiny-pxe-server/>`_ software on your Windows computer. Download this software and extract it on your computer.
|
||||
|
||||
1. Navigate to the folder where you extracted the *Tiny PXE* software and edit the ``config.ini`` file. Directly under the ``[dhcp]`` tag, add the following line: ``rfc951=1`` then save and close the file.
|
||||
|
|
@ -143,97 +200,24 @@ Alternate Process
|
|||
|
||||
5. Continue holding the reset button until you see ``TFTPd: DoReadFile: recovery.bin`` in the Tiny PXE log window.
|
||||
|
||||
6. Release the node’s reset button and click the *Offline* button in Tiny PXE. You are finished using Tiny PXE when the firmware image has been read by the node.
|
||||
6. Release the node’s reset button and click the *Offline* button in Tiny PXE. You are finished using Tiny PXE when the firmware image has been read by the node.
|
||||
|
||||
*Final Configuration Steps*
|
||||
|
||||
1. Configure your computer’s Ethernet network interface to use DHCP for obtaining an IP address from the node.
|
||||
Final Configuration Steps
|
||||
1. Configure your computer’s Ethernet network interface to use DHCP for obtaining an IP address from the node. You may need to disconnect and reconnect your computer's network cable to ensure that your IP address has been reset.
|
||||
|
||||
2. After the node reboots, open a web browser and enter the following URL: ``http://localnode.local.mesh`` Some computers may have DNS search paths configured that require you to use the `fully qualified domain name (FQDN) <https://en.wikipedia.org/wiki/Fully_qualified_domain_name>`_ to resolve *localnode* to the mesh node's IP address.
|
||||
|
||||
3. Navigate to the *Setup* page and configure the new “firstboot” node as described in the **Basic Radio Setup** section.
|
||||
|
||||
Mikrotik First Install Process
|
||||
GL-iNet First Install Process
|
||||
------------------------------
|
||||
|
||||
**Mikrotik** devices must be flashed using steps that are similar to the alternate TP-LINK process described above. Your computer must run a TFTP/Bootp server in order to provide firmware images to Mikrotik nodes. Mikrotik nodes require a **two-part install** process: First, install and boot the correct mikrotik-vmlinux-initramfs file with the **elf** extension, and then use the in-memory-only AREDN |trade| Administration UI to complete the installation of the appropriate mikrotik-rb file with the **bin** extension.
|
||||
**GL-iNet** devices allow you to use the manufacturer's pre-installed *OpenWRT* web interface to upload and apply new firmware images. Check the GL-iNet documentation for your device if you have questions about initial configuration. Both GL-iNet and AREDN |trade| devices provide DHCP services, so you should be able to connect your computer and automatically receive an IP address on the correct subnet. GL-iNet devices usually have a default IP address of 192.168.8.1, so if for some reason you need to give your computer a static IP address you can use that subnet.
|
||||
|
||||
**Preparation**
|
||||
After the GL-iNet device has been 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. Be sure to uncheck/deselect the "Keep Settings" checkbox, since GL-iNet settings are incompatible with AREDN |trade|. After the device has rebooted to the AREDN |trade| image, you should be able to navigate to ``http://192.168.1.1`` for the firstboot or NOCALL page to appear.
|
||||
|
||||
1. Download the appropriate Mikrotik **elf** and **bin** files. Rename the *elf* file to ``rb.elf`` and keep the *bin* file available for later.
|
||||
|
||||
2. 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 Mikrotik devices use the 192.168.1.x subnet by default, so you can give your computer a static IP such as 192.168.1.100 with a netmask of 255.255.255.0.
|
||||
|
||||
You can choose any number for the fourth octet, as long as it is not the same as the IP address of the node and is not within the range of DHCP addresses you will be providing in step 2 below. 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 use different default subnets, such as QRT units which use 192.168.88.x. Select a static IP for your computer which puts it on the same subnet as your device.
|
||||
|
||||
3. 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. If you are flashing a Mikrotik hAP ac lite device, connect the Ethernet cable from *Port 1* of the Mikrotik to the dumb switch.
|
||||
|
||||
**Linux Procedure**
|
||||
|
||||
1. Create a directory on your computer called ``/tftp`` and copy the ``rb.elf`` file there.
|
||||
|
||||
2. Determine your computer’s Ethernet interface name with ``ifconfig``. It will be the interface you set to 192.168.1.100 above. You will use this interface name in the command below as the name after ``-i`` and you must substitute your login user name after ``-u`` below. Use a ``dhcp-range`` of IP addresses that are also on the same subnet as the computer: for example 192.168.1.110,192.168.1.120 as shown below.
|
||||
|
||||
3. Become ``root`` and open a terminal window to execute the following dnsmasq command:
|
||||
|
||||
>>>
|
||||
(root)# dnsmasq -i eth0 -u joe --log-dhcp --bootp-dynamic \
|
||||
--dhcp-range=192.168.1.110,192.168.1.120 -d -p0 -K \
|
||||
--dhcp-boot=rb.elf --enable-tftp --tftp-root=/tftp/
|
||||
|
||||
4. With the PoE unit powered off, connect the Mikrotik node to the POE port. Press and hold the reset button on the Mikrotik while powering on the PoE unit or the hAP device.
|
||||
|
||||
5. 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 about ten seconds. Release the reset button as the computer starts communicating with the node. When you see the "sent" message, this indicates success, and the node has downloaded the image and will reboot. You can now <ctrl>C or kill dnsmasq.
|
||||
|
||||
**Windows Procedure**
|
||||
|
||||
You will need `Tiny PXE <http://reboot.pro/files/file/303-tiny-pxe-server/>`_ software on your Windows computer. Download this software and extract it on your computer.
|
||||
|
||||
1. Navigate to the folder where you extracted the *Tiny PXE* software and edit the ``config.ini`` file. Directly under the ``[dhcp]`` tag, add the following line: ``rfc951=1`` then save and close the file.
|
||||
|
||||
2. Copy the ``rb.elf`` file into the ``files`` folder under the Tiny PXE server directory location.
|
||||
|
||||
3. Start the Tiny PXE server exe and select your Ethernet interface IP 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
|
||||
|
||||
4. With the PoE unit powered off, connect the Mikrotik node to the POE port. If you are flashing a Mikrotik hAP ac lite device, connect the LAN cable from *Port 1* of the Mikrotik to the dumb switch.
|
||||
|
||||
5. Press and hold the reset button on the node while powering on the PoE unit or the device. Continue holding the reset button until you see ``TFTPd: DoReadFile: rb.elf`` in the Tiny PXE log window.
|
||||
|
||||
6. Release the node’s reset button and click the *Offline* button in Tiny PXE. You are finished using Tiny PXE when the firmware image has been read by the node.
|
||||
|
||||
**Final Configuration Steps**
|
||||
|
||||
1. After booting the AREDN firmware image the node should have a default IP address of 192.168.1.1. Change your computer’s Ethernet interface to DHCP mode to obtain an IP address from the node.
|
||||
|
||||
.. attention:: For the *Mikrotik hAP ac lite* **only**, pull 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. If this does not work, then something is wrong. 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 navigate to the *Setup > Administration > Firmware Update* section. Select the **bin** file you previously downloaded and click the *Upload* button.
|
||||
|
||||
As an alternative to using the node's web interface, if your node has plenty of free memory you can copy the **bin** file to the node and run a command line program to install the image. This will allow you to see any error messages that are not displayed when using the web interface upgrade procedure. Execute the following commands from your 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
|
||||
|
||||
3. After the node reboots, navigate to the node’s *Setup* page and configure the new “firstboot” node as described in the **Basic Radio Setup** section.
|
||||
|
||||
GL-iNET First Install Process
|
||||
------------------------------
|
||||
|
||||
**GL-iNET** devices allow you to use the manufacturer's pre-installed *OpenWRT* web interface to upload and apply new firmware images. Check the GL-iNET documentation for your device if you have questions about initial configuration. Both GL-iNET and AREDN devices provide DHCP services, so you should be able to connect your computer and automatically receive an IP address on the correct subnet. GL-iNET devices have a default IP address of 192.168.8.1, so if for some reason you need to give your computer a static IP address you can use that subnet.
|
||||
|
||||
After the GL-iNET device has been 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. Be sure to uncheck/deselect the "Keep Settings" checkbox, since GL-iNET settings are incompatible with AREDN. After the device has rebooted to the AREDN |trade| image, you should be able to navigate to ``http://192.168.1.1`` for the firstboot or NOCALL page to appear.
|
||||
|
||||
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/2/troubleshooting/debrick/>`_
|
||||
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/2/troubleshooting/debrick/>`_
|
||||
|
||||
Post-Install Steps
|
||||
------------------
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ When selecting a device for your AREDN |trade| hardware there are several things
|
|||
* Some older or lower cost devices have a limited amount of onboard memory, but firmware images continue grow in size and functionality. Consider purchasing a device with more memory over one with less memory.
|
||||
* Check the maximum power output of the device, since some devices have lower power capabilities.
|
||||
|
||||
One of the best sources of detailed device information is a manufacturer's datasheet, usually available for download from the manufacturer's website. Currently AREDN |trade| supports over fifty device models from manufacturers including GL-iNET, Mikrotik, TP-LINK, and Ubiquiti Networks.
|
||||
One of the best sources of detailed device information is a manufacturer's datasheet, usually available for download from the manufacturer's website. Currently AREDN |trade| supports over fifty device models from manufacturers including GL-iNet, Mikrotik, TP-LINK, and Ubiquiti Networks.
|
||||
|
||||
If you are just getting started with AREDN |trade| you can easily begin with one of the low-cost devices that comes with an integrated antenna and a :abbr:`PoE (Power over Ethernet)` unit. If you are expanding your AREDN |trade| network with more sophisticated equipment, you may choose a standalone radio attached to any of several kinds of high-gain antennas.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Use a stepped approach to firmware upgrades
|
|||
Clear the web browser cache
|
||||
When using a web browser to perform an upgrade, be sure to clear the browser's cache to remove any cached pages remaining from your node's previous firmware version. A clear cache will help to eliminate confusion when displaying node data in the browser.
|
||||
|
||||
Free node resources
|
||||
Release node resources
|
||||
Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
|
||||
|
||||
You may also want to stop node programs or services that are not needed during the upgrade. For example, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver.
|
||||
|
|
@ -23,8 +23,21 @@ Tips for legacy nodes with low memory (32mb)
|
|||
Legacy equipment with only 32mb of memory will become more difficult to upgrade as the footprint of firmware images continues to grow. Be sure not to use these types of devices at sites which are difficult to access. The sysupgrade process needs around 10mb of free memory to succeed.
|
||||
|
||||
* You may need to try the sysupgrade procedure several times before it succeeds. Be patient and keep trying.
|
||||
|
||||
* Get everything ready to do the upgrade, then do a fresh reboot of the node and immediately start the sysupgrade process before the node has time to initialize services which use memory.
|
||||
* Use command line access to copy the *sysupgrade.bin* image to the /tmp directory on the node, then run the sysupgrade process manually from the command line on the node. This procedure is described in the *Troubleshooting Tips* section of **Installing AREDN Firmware**.
|
||||
|
||||
* Use command line access to copy the *sysupgrade.bin* image to the /tmp directory on the node, then run the sysupgrade process manually from the command line on the node. Note that AREDN |trade| nodes use port 2222 for secure copy/shell access.
|
||||
|
||||
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
|
||||
|
||||
To transfer the image from a Windows computer you can use a *Secure Copy* program such as `WinSCP <https://winscp.net>`_. Then use a terminal program such as `PuTTY <https://www.chiark.greenend.org.uk/~sgtatham/putty/>`_ to connect to the node via ssh or telnet in order to run the sysupgrade command shown as the last line above.
|
||||
|
||||
* As a last resort, use the TFTP procedure to load the *factory.bin* firmware image to the node. This procedure is described in the *First Install* sections of **Installing AREDN Firmware**.
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue