I just flashed a Ubiquiti Bullet with bbhn-1.01-ar71xx-ubnt-bullet-m-squashfs-factory.bin

After the firmware upload was complete, the DHCP in the bullet is assigning my computer an IP: 192.168.1.23, instead of one of the Class A addresses the rest of the mesh nodes assign.  DHCP also assigns a gateway of 192.168.1.1.  I try to ping that IP, and there is nothing there.  A broadcast ping did not reveal any other IP's on the LAN.

Did I brick my bullet?  How can I recover?

Edit: I should have mentioned that localnode:8080 does not get to the config screen either.

I was able to recover back to the Ubiquiti OEM firmware using TFTP. I just tried attempted another upload of the BBHN firmware (1.0.1) and I am back to the same problem.  I uploaded the 1.0.1 version a few more times and could never get to the config screen.

I uploaded the 1.1.2 firmware, I can configure just fine.  I was able to upload the 1.1.2 firmware, then downgrade back to the 1.0.1 firmware, and everything is working fine now.

My Laptop tries to do an identify network when I connect to a new node.  It usually needs a minute or so to do this and it blocks the laptop from connecting to the node until it is finished.  I can tell it is finished by the icon in the lower right for the network changing.  Clearing out the old network identifications seemed to help.

The other thing I recommend when setting up a node is to turn off/disable the WIFI  connection on the Laptop.  They compete against each other and cause problems.

For UBNT devices:

Set a Static ip for the network port on your computer to an address in the 192.168.1.xxx space, where xxx does not equal 1, 20 or 255.  I normally use 100.  That seems to help with the network id. 

Plug in an Ethernet cable between your computer and the ubnt device.  Wait for the computer to id the network.  It may tell you that you don't have an connection to the internet.  That's fine.

Then log into the ubnt device, admin screen, update firmware.

Once the node has rebooted, I usually go back into the lan port and change it to get assignment automatically.  This normally is not necessary since the ubnt is in access mode and uses 192.168.1.xxx addresses.  Make sure you set your DNS to automatically assign as well.

Wait for the network to id and then do the localnode:8080 to set it up.  Some computers require a fully qualified domain name so if localnode:8080 doesn't work try localnode.local.mesh:8080.  You may want to try 192.168.1.1:8080 as well.

If that doesn't work then unplug the network cable, turn on the wifi connection and look for an SSID called meshnode.  Connect to it and then try the localnode:8080 or localnode.local.mesh:8080

I hate to say it but if all that fails your best shot is to use a computer with linux on it and follow the same steps.  The network id is not a problem in Linux.

I also believe you will find you want to be on the latest release.  Most people will be updating and 1.1.2 does not talk to the 1.0.1 devices.  Even you don't connect to anyone else the 1.1.2 fixes some security bugs that you want fixed.

Clint, AE5CA