I thought something like this had been mentioned somewhere on this board, but can't find it. Anyway, I just got a NanoStation Loco M9, and ran the Uboot test. Had to change the OS to 5.5.x and was successful, and it passed the Uboot test. Then went to put aredn on it, but the M9 would barf (saying something like a checksum or such was bad. I had downloaded the file earlier that day. Then I found that I had downloaded the same file a few weeks ago when I did my Bullet M2. That file was accepted and worked fine. So, either the file on the Aredn web site is corrupted, or maybe the filename, having an appended (1) just before the .bin makes a difference. (If the testing the AirOS does to validate the new file uses the file's name).
I'm only posting this as a possible heads up if it turns out the file http://downloads.aredn.org/firmware/ubnt/AREDN-3.16.1.0-ubnt-bullet-m-sq...
is corrupted.
I'm only posting this as a possible heads up if it turns out the file http://downloads.aredn.org/firmware/ubnt/AREDN-3.16.1.0-ubnt-bullet-m-sq...
is corrupted.
Andre