It seems the last several (I don't remember) releases of Aredn think and know that the PBE-M5-400 runs and only runs ;that firmware is (ath79/generic) ubnt (rocket-m-xw).
An internal upgrade in the Firmware window attempts to put on 4.26.1.0. It runs, but doesn't know any thing outside of my LAN for the mesh. It installs the firmware for the PBE-M5-400 as like above, ath79/generic ubnt rocket-m-xw. It also says in the main screen of 4.26.1.0 that I have a Ubiquiti Powerbeam M5 400, which is what I have.
The properly named firmware, regardless of what version, factory or sysupgrade image, fails.
My friend has almost the same hardware setup, and gets the same results.
Even just a spare PBE-M5-400 and a computer isolated from everything else gets the same results.
3.25.10.0 runs just fine. Again, its ath79/generic ubnt rocket-m-xw... other firmware fail.
Ideas? Questions? I thought it might be a vlan issue on my EdgeRouter-X, but the dish isolated does the same thing.
Does anyone else see this issue, or have firmware that works? Should I just wait until the next release of Aredn?
An internal upgrade in the Firmware window attempts to put on 4.26.1.0. It runs, but doesn't know any thing outside of my LAN for the mesh. It installs the firmware for the PBE-M5-400 as like above, ath79/generic ubnt rocket-m-xw. It also says in the main screen of 4.26.1.0 that I have a Ubiquiti Powerbeam M5 400, which is what I have.
The properly named firmware, regardless of what version, factory or sysupgrade image, fails.
My friend has almost the same hardware setup, and gets the same results.
Even just a spare PBE-M5-400 and a computer isolated from everything else gets the same results.
3.25.10.0 runs just fine. Again, its ath79/generic ubnt rocket-m-xw... other firmware fail.
Ideas? Questions? I thought it might be a vlan issue on my EdgeRouter-X, but the dish isolated does the same thing.
Does anyone else see this issue, or have firmware that works? Should I just wait until the next release of Aredn?
Hi, Nick:
Are you installing factory or sys-upgrading AREDN firmware?
on a powerbeam-m5-xw with aredn-3.25.10.0-ath79-generic-ubnt_powerbeam-m5-xw-squashfs-factory.bin ?
or aredn-3.25.10.0-ath79-generic-ubnt_powerbeam-m5-xw-squashfs-sysupgrade.bin ?
or are you attempting to sys-upgrade a pbe-m5-400 running rocket firmware ?
"My friend has almost the same hardware setup, and gets the same results."
Is your friend upgrading from rocket firmware on a non-rocket device?
73, Chuck
Feeding the actual powerbeam factory image through the tftp procedure works.. it took the firmware and presented the first boot (good thing I wrote down the critical stuff) and once basically setup, used the wan port properly.
Once I finished updating my settings I ran the backup, so I have a version 4.x backup.. it says no guarantee during the restore.
Its been running 4.26.1.0 for over 24 hrs now, and no hiccups that I know of.
Will keep my eyes on it...
Nick