diff --git a/files/www/cgi-bin/admin b/files/www/cgi-bin/admin index 9ee2806d..d61b18d2 100755 --- a/files/www/cgi-bin/admin +++ b/files/www/cgi-bin/admin @@ -298,8 +298,7 @@ if($fw_install and -f "$tmpdir/firmware")

If you are connected to the LAN of this node you may need to acquire a new
DHCP lease and reset any name service caches you may be using.

The node will reboot twice while the configuration is applied
-Wait for the Status 4 LED to start blinking, then stop blinking twice.
-When the Status 4 LED is solid on you can get your new DHCP lease and reconnect with
+When the node has finished booting you can get your new DHCP lease and reconnect with
http://$node.local.mesh:8080/
(This page will automatically reload in 3 minutes)

@@ -320,8 +319,7 @@ When the Status 4 LED is solid on you can get your new DHCP lease and reconnect

The node is rebooting

If you are connected to the LAN of this node you may need to acquire a new
DHCP lease and reset any name service caches you may be using.

-

Wait for the Status 4 LED to start blinking, then stop blinking.
-When the Status 4 LED is solid on you can get your new DHCP lease and reconnect with
+

When the node has fully rebooted you can get your new DHCP lease and reconnect with
http://localnode.local.mesh:8080/
(This page will automatically reload in 3 minutes)

diff --git a/files/www/cgi-bin/perlfunc.pm b/files/www/cgi-bin/perlfunc.pm index 33793bb4..fc3efc98 100644 --- a/files/www/cgi-bin/perlfunc.pm +++ b/files/www/cgi-bin/perlfunc.pm @@ -327,8 +327,7 @@ sub reboot_page print "

$node is rebooting


\n"; print "

The LAN subnet has changed. You will need to acquire a new DHCP lease
"; print "and reset any name service caches you may be using.


\n"; - print "

Wait for the Status 4 LED to start blinking, then stop blinking.
\n"; - print "When the Status 4 LED remains solid on you can get your new DHCP lease and reconnect with
\n"; + print "

When the node reboots you get your new DHCP lease and reconnect with
\n"; print "http://localnode.local.mesh:8080/
or
\n"; print "http://$node.local.mesh:8080/

\n"; } diff --git a/files/www/cgi-bin/tunfunc.pm b/files/www/cgi-bin/tunfunc.pm index efee2853..612783e3 100644 --- a/files/www/cgi-bin/tunfunc.pm +++ b/files/www/cgi-bin/tunfunc.pm @@ -221,8 +221,7 @@ sub install_vtun { print "

The node is rebooting

-

Wait for the Status 4 LED to start blinking, then stop blinking.
- When the Status 4 LED is solid on you can reconnect with
+

When the node has fully rebooted you can reconnect with
http://$node.local.mesh:8080/

diff --git a/files/www/help.html b/files/www/help.html index cfe75cf0..737de1b2 100644 --- a/files/www/help.html +++ b/files/www/help.html @@ -724,34 +724,24 @@ in the appendix.

Failsafe Mode

-Failsafe Mode is a method of booting a node into a minimal configuration which -allows you to log in and undo a change that may have broken the node or to -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. +Failsafe Mode is a method of restoring a node to an +operational state.

-How to use failsafe mode: +Reset Password or DHCP: +

- +

+After the node fully boots press and hold the reset +button for 5 seconds which will cause the unit to enable DHCP +and reset the root password to 'hsmm'. +

-Now power cycle the node and it should accept your new password. +

+Full Failsafe:

-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 just been flashed with the AREDN™ firmware.