Using the GUI I dragged-n-dropped
aredn-902-9566393-gl-usb150-sysupgrade.bin
into the 'drag-n-drop' window in the GUI.
Auto-GUI-firmware reboot started and failed to restart.
I get no DHCP assigned address from the USB.
Cold boot failS.
I found this debrick instruction:
https://docs.gl-inet.com/en/3/troubleshooting/debrick/
I found device enx00e04c360157
ifconfig enx00e04c360157 192.168.1.1
Still no response.
:-|
How do I debrick my GL-USB-AR150?
How do I, now, load [GL-iNet / aredn] firmware?
Chuck
You also need to uncheck the Keep Settings box.
See you at Hamvention!
Andre
When I load the .bin file into the 'Firmware Uprade' section of the GUI and the unit GUI bar says something like "Unit rebooting, please wait XX more seconds." and then it usually never comes back on line - with the AREDN firmware, anyway.
I have will not switch to DHCP. I put my laptop's Ethernet on manual 192.168.8.5 and I throw 'http://192.168.8.1:8080/' into the web browser and my NOCALL webpage comes up. Depending on your browser/OS you may have to type only "http://192.168.8.1" into your browser for the NOCALL page to come up. Once I make my node changes and hit 'save changes' and reboot the node - that is when I change my laptop's Ethernet to DHCP and after the node reboots, bring it up on "http://localnode.local.mesh:8080/cgi-bin/status".
For whatever reason the GL devices don't give out DHCP 'more often than not' until it's modified and rebooted.
-Damon K9CQB
Andre, Damon, Ken, M1BKF:
Thanks.
Doh! I didn't think about the iNet default 192.168.8.1.
Device was not bricked.
It was still on 192.168.8.1 in 'N0CALL' state. :-)
Laptop: ifconfig <ethernet device name> 192.168.8.2
I configured from NOCALL.
I set Node Name and Distance to Farthest Neighbor.
I omitted setting a Password, because I got admin access using
the admin password I set when I first booted this device in GL firmware.
Device auto-rebooted when I clicked 'Save Settings'.
Error!
I found the device still on 192.168.8.1, no DHCP, and still NOCALL.
Important! It appears that one must set a password.
I set Node Name, Distance to Farthest Neighbor, and password.
Device auto-rebooted when I clicked 'Save Settings'.
Rebooted laptop to clear static IP address.
Voila!
Node responded to localnode:8080
Thanks, Y'all.
I see that folks are already coming up with innovative AREDN uses for this device.
Chuck
I thought mine was bricked - I was doing power on reset etc.
At some point, I realized I had the laptop plugged into the WAN port.
I moved the connection to the LAN port and there was "nocall" waiting for me ready to set up, DHCP and all.
Ken
When I flashed mine, I unfortunately kept the settings. This gave me a broken AREDN system on 192.168.8.1, without DHCP. I think it was the "plug in with the reset held" that wiped the stale settings and got a working, blank, system.