ARES Forums

Notifications
Clear all

GL-Inet AR-150 and AR-300 Firmware Installation Troubleshooting Tips

1 Posts
1 Users
1 Likes
290 Views
(@k0dz)
Member Admin
Joined: 3 years ago
Posts: 9
Topic starter  

A few issues I've run into while installing firmware on the GL-Inet AR-150 and AR-300 Routers and the fixes:

 

1) Make sure the AR-300 router you purchase has the specific GL-Inet firmware required according to the Supported Platform Matrix 

There is a version of the AR-300 that looks identical to the AREDN-compatible version, but isn't.   There's no way to install AREDN firmware on that non-supported device.

 

2) Avoid the Google Chrome browser while installing firmware.  For whatever reason many people have issues while using Chrome.  I've used EDGE and Firefox successfully.

 

3) Once you get firmware loaded on the node for the first time, usually you can access the new node with localnode.local.mesh:8080       

If that doesn't work, try http://localnode.local.mesh:8080

 

4) If you load firmware and then access the node for the first time, and the node name doesn't show NOCALL-xxxxxxx  as the node name (if the name is blank), there is an issue and usually the node will not accept a new name.   Try powering off the node for a few seconds.  Upon power-up this may allow the proper NOCALL-xxxxxx stuff to appear, indicating that you can successfully rename the node and get on with the configuration.

 

5) If you go into setup and make a change and then lose connection to the node, you can usually get back into the node using localnode.local.mesh   You'll find that the node did not accept the changes.  This is a browser issue.  I've most-often had this occur due to loading firmware onto several nodes in succession.   Try clearing your browser cache.  If that doesn't fix it, clear your cache again and close your browser and reopen it.  If that doesn't fix it, clear your cache once more, close the browser, and reboot your computer. As a last resort, install any required OS updates and any optional updates affecting the Ethernet or Wifi hardware.   I've had to do all of this at one time or another.


   
John Fuller reacted
Quote
Share: