NanoBridge updated well using GUI in admin tab. 2 different Rockets seemed normal through TFT file transfer. Multiple reset attempts with factory version behaved the same. There seems to be no RF out. ipconfig returns ip address 169.254.182.10. address used in edge browser returns "refused to connect".
Anyone else experiencing Rockets bricked but NanoBridges update fine?
You are here
M9 Rockets bricked; M9 NanoBridge updates to 3.21.4.0;
Fri, 06/11/2021 - 18:42
#1
WY7MAE
M9 Rockets bricked; M9 NanoBridge updates to 3.21.4.0;
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
You will likely/hopefully find a better response here later, but
169.254.x.x is typical trait of windoze assigning an address to a device when
a DHCP server is not found.
Likely 168.254.182.10 is the address that windoze assigned to the ethernet device in your computer.
In the TFTP procedure, first you assign a static address to your computer's ethernet device.
After the transfer, the computer is set to obtain an address via DHCP.
Is there any chance that your computer is not set to DHCP mode?
Why are you saying that they are 'bricked'?
Can the rockets be placed into 'TFTP mode?
Chuck
Merlin
i have had to wait up to 8 minutes before the device's DHCP service is active.
I think 3.20.x.x and later firmware responds to :80 and :8080.
So, http://localnode.local.mesh is sufficient.
Like Tom mentioned, clear cache or try another browser or another computer or reboot.
i hope this helps,
Chuck
192.168.1.1 initially as I recall.
There appear to be older Rocket M900 with USB ports and newer M9 non-USB versions in Merlin's network.
We have been able to update the newer non-USB version to 3.21.4.0 through the standard administration setup interface. All newer Rocket M2/M5/M9 devices appear to use the same target firmware (an ath79 type).
With the M900 USB version, the device becomes unreachable after the update, similar symptoms as discussed in earlier discussions regarding updating the Rocket M2 and M5 USB versions-unresponsive, no LED on right, no DHCP, can't ping after reset, etc. The device can be reset and placed in tftp mode with a long button press.
Since then, there is now firmware in the nightly builds generic folder designated ar71xx-ubnt-rocket-m for the M2/M5 models with USB.
Since changes were made to nightly builds to accommodate the Rocket M5/M2 with USB, with ar71xx I decided to flash the M900 USB with the nightly build 613 factory version with the tftp method. This solved the issue and the device is back working again. I have not tried the sysupdate on other M900 USB devices.
I plan to add the Rocket M900 with USB description to all of these nodes in the information header so that others will not make the mistake of updating these with the ath79 firmware.
Make sure you know which device you are updating if you have a mixture of old and newer Rocket M devices on the network.
BTW, it apparently is a mystery why the models included a USB port. It appears to have not been implemented by Ubiquiti and isn't functional.
It would be good to add this to the snapshots readme file as the Rocket M900 with USB isn't a listed device.
-Brett, KG7GDB
Willamette Valley Mesh Network