I have an M900 rocket and it has never been flashed for AREDN.
Every time I try to flash it with AREDN (aredn-3.24.6.0-ath79-generic-ubnt_rocket-m-squashfs-sysupgrade.bin), tftp fails with "Error on server. Firmware check failed". Interestingly, if I use the factory load (aredn-3.24.6.0-ath79-generic-ubnt_rocket-m-squashfs-factory.bin), it loads without error.
Help?
Every time I try to flash it with AREDN (aredn-3.24.6.0-ath79-generic-ubnt_rocket-m-squashfs-sysupgrade.bin), tftp fails with "Error on server. Firmware check failed". Interestingly, if I use the factory load (aredn-3.24.6.0-ath79-generic-ubnt_rocket-m-squashfs-factory.bin), it loads without error.
Help?
If AREDN firmware is loaded, AirOS should not be running.
If, "I have an M900 rocket and it has never been flashed for AREDN."
Then the first AREDN load should be the factory.bin...not the sysupgrade.bin.
Something is amiss.
73, Chuck
Usually these go smoothly...
Update. Power LED is on solid and first red LED is flashing at a 3 second rate. It is not pingable (192.168.1.1). Perhaps I have a bad rocket?
the LEDs dance all around and then settle down to just the Power and one red one flashing at a couple second rate.
Then what?"
According to the documentation:
(https://docs.arednmesh.org/en/latest/arednGettingStarted/installing_firm...)
'5. The node will now automatically reboot with the new AREDN® firmware image.'
"It is not pingable (192.168.1.1)."
Yes, after booting AREDN firmware, it is not pingable at 192.168.1.1.
Set your computer to obtain an IP address via DHCP.
Restart networking on your computer.
I hope this helps,
Chuck
And yes, I've restarted the networking on the notebook I'm using with no IP being assigned still
In many urban areas (and I would assume the Silicon Valley would be included), the 900 MHz band is massively choked with both licensed and part 15 operations. I would suspect that to get a decent throughput, your link distance would be limited to very short distances. Be fine to get across the street, but may not be much more than that.
As for 900, yea. I am aware of the clatter and noise floor issues. Fortunately where these radios will be deployed, that shouldn't be an issue. The site in question is heavily forested so 2.4 or 5.8 is out of the question. And the other end if rural as well, not urban. Guess the only way I'll know for sure is to try it!
Thanks for the help, guys.
AREDN-3.16.1.1-ubnt-rocket-m-squashfs-factory.bin loads fine via tftp. I can then go in, change passwords, etc and am able to reach the rocket, both over the air and via LAN. (I took a working Nano Loco and connected it to Port 5 of my local hAP).
As soon as I upgrade either rocket to aredn-3.24.6.0-ath79-generic-ubnt_rocket-m-squashfs-sysupgrade.bin, after it reboots, I cannot reach it via LAN nor RF. The only fix is to reload AREDN-3.16.1.1-ubnt-rocket-m-squashfs-factory.bin again.
Starting with version 3.16.1.1, I then upgraded :
3.18.9.0 - good
3.19.3.0 - good
3.20.3.1 - no good. No further comm with the node, either via LAN or RF is possible.
Maybe this info points towards something useful.
I found the solution here:
https://www.arednmesh.org/comment/18273#comment-18273
The latest release I loaded was aredn-3.21.4.0-ar71xx-ubnt-rocket-m-sysupgrade.bin as that seems to be the latest ar71xx version available in the archives. Where would be the appropriate place to ask about a later release built for the USB-equipped rocket?