Hello,
I currently have a UBNT Rocket M2 running AirOS v6.0.7 and have not been successful in getting it downgraded to a firmware version that supports AREDN. I even tried the 6.0.6 beta firmware, but the Rocket will not accept this as it is v6.0.7. Does anyone have a firmware path that will enable the device to downgrade? Thanks
73,
Jacob
I currently have a UBNT Rocket M2 running AirOS v6.0.7 and have not been successful in getting it downgraded to a firmware version that supports AREDN. I even tried the 6.0.6 beta firmware, but the Rocket will not accept this as it is v6.0.7. Does anyone have a firmware path that will enable the device to downgrade? Thanks
73,
Jacob
https://www.aredn.org/content/uploading-firmware-ubiquiti (about 1/3 of the way down the page)
I had to use the nightly build method to flash a NSM3 that would not take any of the UBNT firmware via TFTP. Will there be any issues using the nightly build on that device in an AREDN-3.16.1.1 network? Would it be best to TFTP the unit with the current stable release firmware, AREDN-3.16.1.1?
73,
Jacob
in other words, if you had AirOS 6.x on it and loaded the nightly, YOU SHOULD NOT load AREDN 3.16.1.1 on it.
From the nightly page it said to use loco-m-xw version for the M2
any thoughts on what I maybe doing wrong?
73
Darrell
http://downloads.arednmesh.org/snapshots/trunk/targets/ar71xx/generic/ar...
Confirm this is the image used for the tftp?
Joe AE6XE
I'm confused. There are two different devices being discussed in this thread. Rocket and a Nanostation. If you have a Nanostation, is it an "XM" or "XW" model? I suspect that if is rejecting the loco-m-xw file, then, it may be an "xm" model. Is so, you should use the bullet-m file as noted in the readme. http://downloads.arednmesh.org/snapshots/trunk/readme.md
Let us know if this is the case or not.
Good luck!
K5DLQ - Darryl
Sorry it is a Rocket2 xw with airvos 6.1.5 I was following
KF4HJW, any luck yet? Tricks often used:
1) have a (dumb) switch that both the laptop and device plug into. It keeps the ethernet link up on both devices all the time.
2) after the tftp image is "sent", in binary mode, and there are no errors. Then, put the laptop back into DHCP mode and look to see if it is getting an IP address.
3) When node is changing around with various IP addresses and/or rebooting, I often pull the cable on the laptop for 5 seconds and plug back in, to drop the Ethernet link and force it to set back up on the laptop.
4) If the device has had various older versions of AirOS attempted to load, and older versions of AREDN attempted, then do this procedure to clean up the bootloader settings:
Joe AE6XE
Thanks
Joe AE6XE