Hello all,

I installed the latest MESH firmware onto a UBNT Rocket M2.  All went well.  I had it configured and was connecting fine via the network cabling.  I mistakenly disabled the DHCP check-box and now I can not access the Rocket M2 via the WEB.

I tried the 172 address...no joy.  I tried the 192 address...again no joy. 

I have tried http://localnode.local.mesh:8080 again no joy.

I am able to do a sudo reset and log-on via telnet at 192.168.1.1 to access OPENWRT.  But I can not access the standard WEB interface.  Can you please provide some guidance.

---
Suggestion...I saw in the WEB interface a "RESET" button, is there a way to activate this "RESET" from the OPENWRT command line? As I understand this would bring the installed firmware to a known factory install, thus enabling DHCP.

Or secondarily, a procedure that I can reload the mesh.bin file from the OPENWRD command line so I can start with a fresh install.
---

Please, any assistance would be greatly appreciated.  Thank you for your time.

Paul

WD6EBY

If you are in the node command line run "firstboot"

This will wipe out the volatile partition and restore the node to "just flashed" status,  you can then reboot. You will have to go through setting up the node again.

Also if you ever fully loose access and can't get in you can always use a TFTP install to restore the node http://ubnt.hsmm-mesh.org/products/BBHN/wiki/HowTo/FlashUbiquiti 

Thank you Conrad,

I ended up doing a HARD reset (per your directions) and did a TFTF with the original UBNT firmware.  Under the UBNT tab "SYSTEM" I did a Factory Reset.  Once I was confident that the UBNT firmware was working as it should, I loaded the MESH firmware.  I found that if I did NOT do the FACTORY RESET that the MESH firmware did NOT address properly.  Don't quite understand this yet. 

Once the MESH firmware was uploaded via the UBNT ubgrade GUI, I did a successful initial login with the http://localnode.local.mesh:8080.  From here it is pretty straight forward. ROOT / hsmm and I am in.

Maybe a section could be added in the forum listing procedures such as this.  I am sure this is not the first time this has happened.

I cant tell you how much I appreceate your help

Again Thank you

Paul

WD6EBY...