mirror of https://github.com/aredn/aredn.git
bugfix: Remove references to Status 4 LED
AirRouter does not have a Status 4 LED. The Power LED does similar to the Status 4 on the AirRouter. Changing the text to be more generic removing reference to LED's and leave the documentation of how to know a node has booted to be done elsewhere. fixes AREDN->ticket:208 Change-Id: I8821f86e89e17d25e4a21abfdd94d989619d081a
This commit is contained in:
parent
835d7e021c
commit
60e2310917
|
@ -298,8 +298,7 @@ if($fw_install and -f "$tmpdir/firmware")
|
||||||
<h3>If you are connected to the LAN of this node you may need to acquire a new<br>
|
<h3>If you are connected to the LAN of this node you may need to acquire a new<br>
|
||||||
DHCP lease and reset any name service caches you may be using.</h3>
|
DHCP lease and reset any name service caches you may be using.</h3>
|
||||||
<h3>The node will reboot twice while the configuration is applied<br>
|
<h3>The node will reboot twice while the configuration is applied<br>
|
||||||
Wait for the Status 4 LED to start blinking, then stop blinking twice.<br>
|
When the node has finished booting you can get your new DHCP lease and reconnect with<br>
|
||||||
When the Status 4 LED is solid on you can get your new DHCP lease and reconnect with<br>
|
|
||||||
<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a><br>
|
<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a><br>
|
||||||
(This page will automatically reload in 3 minutes)</h3>
|
(This page will automatically reload in 3 minutes)</h3>
|
||||||
</center></body></html>
|
</center></body></html>
|
||||||
|
@ -320,8 +319,7 @@ When the Status 4 LED is solid on you can get your new DHCP lease and reconnect
|
||||||
<center><h2>The node is rebooting</h2>
|
<center><h2>The node is rebooting</h2>
|
||||||
<h3>If you are connected to the LAN of this node you may need to acquire a new<br>
|
<h3>If you are connected to the LAN of this node you may need to acquire a new<br>
|
||||||
DHCP lease and reset any name service caches you may be using.</h3>
|
DHCP lease and reset any name service caches you may be using.</h3>
|
||||||
<h3>Wait for the Status 4 LED to start blinking, then stop blinking.<br>
|
<h3> When the node has fully rebooted you can get your new DHCP lease and reconnect with<br>
|
||||||
When the Status 4 LED is solid on you can get your new DHCP lease and reconnect with<br>
|
|
||||||
<a href='http://localnode.local.mesh:8080/'>http://localnode.local.mesh:8080/</a><br>
|
<a href='http://localnode.local.mesh:8080/'>http://localnode.local.mesh:8080/</a><br>
|
||||||
(This page will automatically reload in 3 minutes)</h3>
|
(This page will automatically reload in 3 minutes)</h3>
|
||||||
</center>
|
</center>
|
||||||
|
|
|
@ -327,8 +327,7 @@ sub reboot_page
|
||||||
print "<h1>$node is rebooting</h1><br>\n";
|
print "<h1>$node is rebooting</h1><br>\n";
|
||||||
print "<h3>The LAN subnet has changed. You will need to acquire a new DHCP lease<br>";
|
print "<h3>The LAN subnet has changed. You will need to acquire a new DHCP lease<br>";
|
||||||
print "and reset any name service caches you may be using.</h3><br>\n";
|
print "and reset any name service caches you may be using.</h3><br>\n";
|
||||||
print "<h3>Wait for the Status 4 LED to start blinking, then stop blinking.<br>\n";
|
print "<h3>When the node reboots you get your new DHCP lease and reconnect with<br>\n";
|
||||||
print "When the Status 4 LED remains solid on you can get your new DHCP lease and reconnect with<br>\n";
|
|
||||||
print "<a href='http://localnode.local.mesh:8080/'>http://localnode.local.mesh:8080/</a><br>or<br>\n";
|
print "<a href='http://localnode.local.mesh:8080/'>http://localnode.local.mesh:8080/</a><br>or<br>\n";
|
||||||
print "<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a></h3>\n";
|
print "<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a></h3>\n";
|
||||||
}
|
}
|
||||||
|
|
|
@ -221,8 +221,7 @@ sub install_vtun
|
||||||
{
|
{
|
||||||
print "
|
print "
|
||||||
<center><h2>The node is rebooting</h2>
|
<center><h2>The node is rebooting</h2>
|
||||||
<h3>Wait for the Status 4 LED to start blinking, then stop blinking.<br>
|
<h3>When the node has fully rebooted you can reconnect with<br>
|
||||||
When the Status 4 LED is solid on you can reconnect with<br>
|
|
||||||
<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a><br>
|
<a href='http://$node.local.mesh:8080/'>http://$node.local.mesh:8080/</a><br>
|
||||||
</h3>
|
</h3>
|
||||||
</center>
|
</center>
|
||||||
|
|
|
@ -724,34 +724,24 @@ in the appendix.
|
||||||
|
|
||||||
<a name='failsafe'><h3>Failsafe Mode</h3></a>
|
<a name='failsafe'><h3>Failsafe Mode</h3></a>
|
||||||
<p>
|
<p>
|
||||||
Failsafe Mode is a method of booting a node into a minimal configuration which
|
Failsafe Mode is a method of restoring a node to an
|
||||||
allows you to log in and undo a change that may have broken the node or to
|
operational state.
|
||||||
change a forgotten password without having an authorized ssh key in
|
|
||||||
place. Since fixing a node is an advanced topic suitable only for experts,
|
|
||||||
here I will just cover how to change a password.
|
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
How to use failsafe mode:
|
Reset Password or DHCP:
|
||||||
|
</p>
|
||||||
|
|
||||||
<ul>
|
<p>
|
||||||
<li>connect your computer the the LAN port of the node</li>
|
After the node fully boots press and hold the reset
|
||||||
<li>use a static IP address of 192.168.1.2 and netmask 255.255.255.0<br>
|
button for 5 seconds which will cause the unit to enable DHCP
|
||||||
(default gateway and DNS are not necessary)</li>
|
and reset the root password to 'hsmm'.
|
||||||
<li>apply power to the node</li>
|
</p>
|
||||||
<li>just after the Status 4 LED illuminates, hold the reset button until DMZ starts blinking</li>
|
|
||||||
<li>at a command prompt run "<b>telnet 192.168.1.1</b>"</li>
|
|
||||||
<li>you should now have a prompt that looks like "root@(none)$"</li>
|
|
||||||
<ul><li>if not, you are not in safe mode and something went wrong along the way, so stop here and start over</li></ul>
|
|
||||||
<li>type "<b>mount_root</b>"</li>
|
|
||||||
<li>type "<b>setpasswd abc</b>"</li>
|
|
||||||
<ul><li>replace abc with the password you want to use</li></ul>
|
|
||||||
<li>type "<b>exit</b>"</li>
|
|
||||||
</ul>
|
|
||||||
|
|
||||||
Now power cycle the node and it should accept your new password.
|
<p>
|
||||||
|
Full Failsafe:
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
If the device has a reset button you may instead press and hold the reset
|
After the node fully boots press and hold the reset
|
||||||
button for 15 seconds which will cause the unit to behave as if it had
|
button for 15 seconds which will cause the unit to behave as if it had
|
||||||
just been flashed with the AREDN™ firmware.
|
just been flashed with the AREDN™ firmware.
|
||||||
</p>
|
</p>
|
||||||
|
|
Loading…
Reference in New Issue