First sorry for my bad English..
To get things going in the Netherlands we tried to setup some Aredn nodes with not much success.
Setup:
- Ubiquiti Rocket M2 XW with AirOS working just fine.
- Ubiquiti Nanostation M2 Loco XM with AirOS also working fine.
Watched several youtube video's and documentation but I can't access both units after flashing with FW 3.23.4.0 (or any other version). Flashing of the Rocket goes well and all seems to be okay, all led's that should light up do so. Flashing of the Nanostation doesn't go well, after flashing no LAN led and one red led.
Neither units are accessable after flashing and DHCP doesn't work.
Tried differend computers and different TFTP clients to flash, no succes.
I think I'm doing something horribly wrong but can't find out what. Should I first install older AirOS versions to get things going?
Thanks!
Werner PA3GYV
To get things going in the Netherlands we tried to setup some Aredn nodes with not much success.
Setup:
- Ubiquiti Rocket M2 XW with AirOS working just fine.
- Ubiquiti Nanostation M2 Loco XM with AirOS also working fine.
Watched several youtube video's and documentation but I can't access both units after flashing with FW 3.23.4.0 (or any other version). Flashing of the Rocket goes well and all seems to be okay, all led's that should light up do so. Flashing of the Nanostation doesn't go well, after flashing no LAN led and one red led.
Neither units are accessable after flashing and DHCP doesn't work.
Tried differend computers and different TFTP clients to flash, no succes.
I think I'm doing something horribly wrong but can't find out what. Should I first install older AirOS versions to get things going?
Thanks!
Werner PA3GYV
I am having about the same problem. I just purchased a brand new rocket M2 on Amazon. When it got here today, I set it up and connected to AirOS to look at the firmware on it (XW 6..2). I determined it is an XW model, and proceeded to flash with AREDN.
I flashed from: http://downloads.arednmesh.org/releases/3/23/3.23.4.0/targets/ath79/generic/aredn-3.23.4.0-ath79-generic-ubnt_rocket-m-xw-squashfs-factory.bin
Using TFTP from windows computer:
tftp -i 192.168.1.put aredn-3.23.4.0-ath79-generic-ubnt_rocket-m-xw-squashfs-factory.bin
Watched the lights on the rocket, the network light flashes as the transfer happens, then the 1,2,3,4 lights flash in a back and forth sequence as the flash happens. The rocket appears to reboot, then comes up with power, link, on and light 4 flashing (normal for loading AREDN).
Looks so far so good.. But then the #4 light stays on solid, and the ethernet port appears now to be "broken". It does not respond to ping at 192.168.1.1 or 192.168.1.20.
Put back in TFTP mode so lights are flashing 1-3, 2-4, alternating again.. It doesn't respond on 192.168.1.1 or 192.168.1.20 so I cannot attempt to re-flash.
Looks like my rocket is "bricked" at this point. I am hoping someone here has more experience than me and can help me to recover from this.
In you're case I would try to power the unit down and put it in tftp mode again. It should be acceptable via 192.168.1.20. Then flash AirOS again so you have a working unit.
If there is no solution I let Aredn go and build my own network with AirOS, after all, that works solid.
I've been given a pile of NSM5XM and NSM5XW to flash to use for demonstrations and tests.
The current version firmware install never gets past the flashing lights, the command prompt tells me the file transfer failed and the device remains on 192.168.1.20 ... at least I can get back into the factory stuff.
I figured I'd try to put on 3.22.12.0 but I cannot find it in the list of older firmware. There is a generic file that seems to be from the correct date, but when I click the link I get some weird message about download settings ... strange.
Is there any way to get direct links to the older firmware?
Ed
Is the 3.22.12.0 the holy grail? I've tried all the other fw versions (the officials) with no success. Or the node starts up with the fourth led green or the node starts up with the first led red and the last one green. In all cases the node is not accessible or dhcp. It's really frustrating that I can't find out the problem, all is done by the manual..
But if the 3.22.12.0 should work (and is available somewhere) I considering a last try.
http://downloads.arednmesh.org/firmware/html/stable_322120.html
Especially when some of the instructions for going to 3.23.4.0 include language like "first upgrade to 3.22.12.0 or downgrade to 3.22.12.0 before applying" ... if the files aren't easily found this creates a problem ...
No version of the firmware is or could be "The Holy Grail". The advantages of keeping things current is clear, but not always possible in short time frames. I like the new software selection tool ... except when it doesn't have the option I need right now.
Ed K7EOK
This reminds me of PC software slowly not being supported, and the older hardware being phased out. I'm sure it's a headache trying to keep things downwards compatible but it's hard to just replace hundreds of nodes. Somehow this will all get sorted out and we'll move forward.
Thanks again everyone here,
Ed
Here are the instructions for downgrading firmware releases on your node. The older firmware is always available through the AREDN website.
https://docs.arednmesh.org/en/latest/arednHow-toGuides/firmware_tips.html#tips-for-downgrading-firmware
I was able to flash the 3.22.12.0 firmware onto the bullet that I was having trouble with, after flashing it boots up and the first (red) and last (green) LEDS stay lit, but the node responds at 192.168.1.1. I set the node up and let it reboot again, got a DHCP address from it, and got it to talk to my other node across the room. So far all is good.
I then went to upgrade the firmware from within the AREDN software, downloaded the current 3.23.4.0 firmware for sysupgrade, and went onto the bullet node to tell it to upgrade the firmware. I got the screen that said it would upgrade in the background, and then the node rebooted twice. After second reboot, everything is stable on the bullet (lights not flashing, waited like 10 minutes) it has still not given an IP address to the PC via DHCP.
It looks like something changed in the most recent version that causes it not to work. I did have the presence of mind to get a support data dump while it was on 3.22.12.0, and have attached that here, hoping someone can see what is going on here. (I changed the .gz to .tgz so the upload would work).
Got the rocket to come back at 192.168.1.20 again after rebooting it this morning to TFTP mode, and immediately sent it the aredn-3.22.12.0-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin file. (There were two that list Rocket XW, but this one had a "test date after xxx" listed for the loco that it also supported, and the test date on my rocket box is well after that date (1/27/21) so I went with a hunch and tried this one).
The rocket is now up and running on 3.22.12.0 as well. Here is a dump from the rocket, so hopefully people smarter than me can figure out why the newest firmware did not work on it and let me know what path to proceed from here.
Yes, the file that AD7OV mentioned is the one to use. It agrees with the old selector matrix. I believe the new software selector may be giving out the wrong file. I could be wrong. Stay away from the 3.23.4.0 FACTORY file for sure. I can repeatedly break my spare rocket 2M XW with it. The UPGRADE appears to work on some nodes. I'm sticking with 3.22.12.0 for now.
So you should see an explicit nightly build for the Rocket M2 XW tomorrow (or possibly the day after) which should fix that device. You should be able to flash this factory build using the usual "alternative blinky light" tftp method.
Unfortunately I do not have an Nanostation M2 Loco XM and I'm not sure how to source one (eBay listing as not reliable for a specific hardware version).