MAHALO to KC0EUW firmware install steps: https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installin
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® “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® 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
See the GL-iNet firmware is here. Look for files with "-gl-" in the file name.
In a web browser, open the node’s Administration page http://192.168.1.1/
(user = ‘root’ password = ‘hsmm’) and navigate to the Setup >
===
After the GL-iNet device has been booted and configured, navigate to the Upgrade section and click Local Upgrade to select the AREDN® “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® image, you should be able to navigate to http://192.168.1.1 for the firstboot or NOCALL page to appear.
The USB150 is an interesting little device. It basically turns your laptop, tablet, or even cellphone into a mesh-connected node. It's very useful especially during emcomm deployments to access programs and services across the mesh. The radio range is not far, but at a shelter or command post you can mesh together several devices, and then longer-distance connections can be made through other types of nodes that link across a larger geographical area. Another feature is the ability to use it as a remote tunnel client via the "WAN Wifi Client" which connects the radio to a local AP and tunnels back into your mesh network from anywhere you have Internet access while traveling. Fun little device to carry with you almost anywhere.
Orv W6BI
Happens very often. :-|
After the GL-iNet device has been booted and configured, navigate to the Upgrade section and click Local Upgrade to select the AREDN® “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® image, you should be able to navigate to http://192.168.1.1 for the firstboot or NOCALL page to appear.
I agree with what Jim K6CCC replied. A USB-150 could possibly be used as a tunnel client if you set it up as a WAN Wifi Client as described in the docs at the following link:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_config.html#wan-column
As a tunneling node I personally would rather use a GL.iNet AR-150, AR-300M16, AR-750 or a Mikrotik hAP ac lite. All of those have a dedicated WAN port with VLANs already preconfigured.
Topic at top is Steps for flashing GL.iNet GL-USB150 Microuter - YELLOW="RESEARCHING" Under
Earlier I missed your statement: "I cannot get the unit to install the Tunnel software."
That statement seems somewhat vague to me.
I also missed your question: "Is there a way to repair this?"
I will assume that you cannot install the tunnel software because the USB150 does not have an internet connection.
In this case, yes, there is a way to repair this.
Set up the USB150 in WiFi client mode connected to a WiFi AP that has an internet connection.
I hope this helps. Chuck
Jerry, this is a user forum so we're all regular hams just like you. I can't speak for anyone else, but I certainly wouldn't call myself an "expert." All of us have had more or less experience with these nodes -- which means we've all probably made more mistakes and learned from them. Everyone here is just a volunteer, coming together as a community to try helping each other if we can. In my experience with communities like this, you can catch more flies with honey than vinegar.
Steve, I would agree with your statement. By making a request, I am trying to politely ask for help. When a person answers a request on this forum, it would reflect experience beyond what I have, hopefully. I am not new to computers, mesh, routers, or AREDN. I have been actively using Mesh since BBHN first started, and have upgraded all my equipment to all the current AREDN standards. I do appreciate all yours, Jim's and Steve's answers. I began my request with "Joe", hoping to get input from AE6XE, as it appears he had a major part in this particular software development. Now. Having tried all the proposed solutions that I have seen so far, I still have one GL-USB-150, which does have an internet connection to my home LAN, at WAN address 192.168.11.28, that, when I go to SETUP, Tunnel Client, "Tunnel software needs to be installed.", and click on "Click to install", continues to return the ERROR message, " ERROR:Package installation failed!". Is there a further diagnostic available, or is this unit doomed to not having tunnelling available?
If you know how to Telnet or SSH into the node and perform a ping to something on the internet, it will prove beyond a doubt that you really have internet connectivity.
The firmware version is 1866-bf944df
No, I read the warnings, and have not messed with any Advanced Configuration items at all.
SSH'd in, pinged cyberjer.net, received pings back.
It looks like your USB-150 is configured correctly and has WAN Internet access. I booted my USB-150 which also has #1866 and set it up as a WAN Wifi Client. I tried installing the vtun package from the command line so I could see any detailed error messages, and it failed saying it was unable to resolve package dependencies. In the vtun package control file there are four dependencies:
Back on my USB-150 I started installing missing dependencies and once they were installed then the vtun package completed successfully.
I'm not sure why your first USB-150 was able to resolve and install all dependencies but the second one was not. There must be some difference between the two that accounts for what you experienced.
Thanks, Steve. Jim asked if I had messed with the "Advanced Configurations", which I had not. However, I did look at them, and the node that was successful in loading the vtun software does have somewhat different addresses listed on its Advanced Configuration page from what the node I am working on has. So before I commit to trying your solution (which does make good sense) I would like for Jim or someone to tell me if putting some of the files in Advanced Configuration at the settings marked "Set to Default" could solve this situation?
The USB-150 that is running successfully with the vtun software installed: Going into Advanced Configuration
seventh title from the top,
aredn@downloads[0].pkgs_arednpackages
link reads this way:
http://downloads.arednmesh.org/snapshots/trunk/packages/mips_24kc/arednp...
in the project node, seventh title from the top reads the same title,
but link reads this way:
http://downloads.arednmesh.org/releases/3/20/3.20.3.1/packages/mips_24kc...
Does this give anyone a clue?
I got my first clue looking at where you were downloading your dependencies from. Then I compared the go to addresses in Advanced Configuration, and decided the project node had a screwed up set of links. That is why I asked about the Set to Default choice. One does have to tell each position to save the setting once it is changed. Pretty hard to mess up.
Big THANK YOU to AB7PA, K6CCC and NC8Q!!!
Jerry/W0HU