Hi,
I am trying to install on a device that already has Open-wrt 19.07.7 running fine on it.
Initially I tried a sysupdate via the gui as I thought it worth a try as its the same base program. This seemed to work fine but crashed whenever I reset the password as requested, it doesn't re-boot and doesn't ping although the lights look like its working.
If I press the reboot button on the GUI without changing the password it re-boots OK.
So.. I tried the factory image via tftp, again it loads fine but again crashes the GUI and doesn't ping if I re-set the password.
I am using the latest firmware for the Bullet M2(HP) XW.
Tried many re-boots of PC and Bullet, no change.
If I perform a HARD reset it will then load again and I can access it.. UNTIL I change the password, then the comms crash again and I have to re-install or hard reset.
I am loath to try from the original AirOs as they now have a signed firmware system and it was not simple overcoming it to install Open-wrt and if Open-wrt 19.07.7 is working I am a loss to understand what the issue is.
Any suggestions or a work-around? I can't find any older firmware images to try.
Using:
| aredn-3.21.4.0-ath79-ubnt_bullet-m-xw-factory.bin |
I tried the factory image via tftp, again it loads fine but again crashes the GUI
Please confirm that
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#ubiquiti-first-install-process
completes through step 8.
Please confirm that you begin Basic Radio Setup
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/basic_setup.html and
1 enter a new node name that contains only letters, numbers, or a dash;
2 you set a new password, then click 'Save Changes'.
3 Your node reboots.
4 You reset your computer's ethernet port to obtain a new DHCP address.
Please give more detail on what you mean when you say 'crashed' and where in the install procedure the 'crash' happens.
I hope this helps,
Chuck
Hello,
Yes it completes up to step 8.
1 enter a new node name that contains only letters, numbers, or a dash; - YES
2 you set a new password, then click 'Save Changes'. YES
3 Your node reboots. - NO, it tries to re-boot but after the final (No.6) light finally becomes steady on the device, I am unable to ping 192.168.1.1 (or anything on 192.168.1.X, I checked with nmap -sn 192.168.1.0/24 ) or activate the gui and I cannot SSH. (no response)
4 You reset your computer's ethernet port to obtain a new DHCP address. -YES I completely re-booted the PC to make sure after I had waited some time of no response to pings.
When I say 'crashed' I mean it no longer responds to pings, SSH or GUI loading attempts after it tries to re-boot after changing the password. . As I said previously, if I press the re-boot button on the GUI WITHOUT changing the password it re-boots OK.
3 Your node reboots.
Maybe yes.
If you do not set a node name and password and click 'Change Settings',
the node will reboot to 'First Install - Basic Radio Setup' and will
return using 192.168.1.1
(3) If you do set a node name, change the password, and click 'Save Changes',
the node will reboot.
After it reboots, it is no longer on 192.168.1.1.
Reboot your computer or reset your ethernet port to obtain a new address via DHCP.
About 3-9 minutes after (3), your computer should get a 10.x.x.x address from the node.
I hope this helps,
Chuck
Perfect thanks.
Rookie error, forgot I had fixed the pc's IP to the 192.168.1.X subnet as that was required for flashing the device from stock.
All working well now, seems very slick, nice work.
For future searchers, Ubiquiti introduced a signed firmware system and prevented downgrading (for the Bullet M2HP) . A workaround is available on Github, until they change the boot loader again.
Interesting article on it below.
https://owenh.net/bulletm2hp