What would be the best way to load firmware on to a PowerBeam M5 400-ISO? Can I just take a nightly build (if so which one is best - I see a few posts saying I should use the Rocket firmware) and just TFTP it on to the node or do I need to downgrade to Air OS 5.6.15 then 5.5 and then upload the firmware via TFTP or the GUI?
I just want to make sure I don't brick the node.
Thank you,
Dave
I just want to make sure I don't brick the node.
Thank you,
Dave
Dave
Specifically, the PBE-M5-400 models need the "rocket-m-xw" images. There was a table created in this prior post:
https://www.arednmesh.org/content/request-testers-ubiquiti-xw-issues
Joe AE6XE
For those interested in the "table created in this prior post" (above), the newly updated URL is:
https://www.arednmesh.org/content/request-testers-ubiquiti-xw-issues
- Don - AA7AU
I have an in-service pbe-m5-400 running develop-176-8c5be0cf.
I want to over-the-ethernet upload firmware aredn-63-f05c204-f8cc686-ubnt-rocket-m-xw-sysupgrade.bin.
However, when I browse to http://nc8q-pbe-m5-400.local.mesh:8080/cgi-bin/admin
and select the local .bin file, the 'Upload' button is 'grayed out".
Do I need '*factory*.bin' instead?
Must I 'tftp' ?
Regarding the PBE-M5-400:
How do I over-the-air/ethernet upload a 'Nightly-Build' to a device with a 'Nightly-Build' ?
Chuck
------
Note:
-------Files can not be uploaded to a node while a tunnel server or client connection is enabled. To upload any file (firmware, package or ssh key) you must ensure all tunnel servers and clients are disabled.
Upload buttons will be disabled until tunnels are disabled.
You need to disable all tunnel server/client connections.
Thanks Darryl.
Waiting 3 minutes. ;-)
Chuck
Now I have aredn-63-rocket-m-xw-sysupgrade.bin and no vtun.
I cold booted the pbe-m5-400 while holding the reset button on the POE injector,
but the device boots to a normal node status anyway.
Is there a way to reload vtun or any .bin without climbing the tower?
Could the reset button be defective?
Chuck
if you are trying to get the node to "pre-config" state, you can ssh to the node and run: firstboot -y && reboot
After a few mins or so, it will allow you to configure it from scratch. (ie. nodename, passport, distance... )