I have installed the firmware and accessed the setup screen. Upon hitting "save" the screen displayed it would take 60 seconds to reboot. It provided the network address to enter:

localnode.local.mesh:8080

or

wd4hxg-Sterling.local.mesh:8080

to log back in. I tried both but the timeout message was displayed. Running IPCONFIG revealed a 169.x.x.x  address on the RJ-45 port on the computer. See the below take on the Command Line Display where the ipaddress is displayed.

I am currently lost. I have powered down the Bullet and brought it back up. Even after powering back up the default NOCALL-6-173-4 is displayed in the wireless connections window. If I disconnect the RJ-45 Ethernet connection the IP address for the wired lan is not displayed using ipconfig. Reconnecting the RJ-45 the 169.x.x.x address returns.

Any suggestions on accessing the device.

Thanks

Chuck

Well it appears I have created another fine mess. During the setup in the BBHN firmware I set the device to "Access Point" mode. This seems to remove access via the wired ethernet port. There is a discussion on just this problem but if I am reading it correctly the procedure works with Linksys boxes, not Ubiquiti linked to Linksys. 

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-3-firmware/topic-773-changed-node-to-qstandard-access-pointq-cant-get-out-of-it.html

It is not clear to me that this procedure can be used to recover the Ubiquiti device.

Ubiquiti's site has instructions for restoring the original firmware using tftp. Would it work to use their procedure to return the device to the original state or has loading the BBHN firmware forever blocked that option?

I have successfully loaded firmware on Linksys boxes without issue and really am puzzled by the difficulties being encountered with the Ubiquiti device.

easy fix.

power the unit up fully (takes about 60 secs)

press the reset button for 5-6seconds.

access at:  http://localnode:8080

Morning Daryll

Thanks for taking the time to provide the method to

reset the device. Unfortunately it gave me the NATO

salute aka foreign military salute.

OK ---- Here is what I did.

1 Disconnect laptop wireless access to internet.

2 Set Wired LAN on laptop to DHCP

3 Pulled cable on Ubiquiti Bullet at the device for about two minutes

4 Reconnected Wired LAN Cable to Ubiquiti device.

5 Depressed Reset switch for about 10 seconds (if 5 works than 10 should work doubly good.)  :-)

6 Connected LAN cable to laptop.

7 Entered http://localnode:8080 in the URL line of the browser (Firefox)

8 The following screen pops up after timing out:

Checking IPCONFIG I have a non-routeable 169.X.X.X address on the Laptop NIC connected to the Ubiquiti device.

Getting very frustrated. Not to the point of putting the device on the drill press and going for maximum smoke but ideating it.   :-)

Thanks

Chuck

this assumes that you are running firmware 3.x

You might be missing the time ranges by holding it too long. (more is not always better) The hold time ranges/functions are: 3-7 secs to reset password and enable dhcp (basic reset) 12-20 secs to reset to INITIAL state (where you need to specify your callsign and password) If these don't work, you can always do a TFTP firmware load.

Just an observation:

The URL in the screen shot is incorrect.

Should be:

localnode:8080

Hilary

VK2IUW

I used  localnode:8080 and other noted permutations such as:

                      localnode.local.mesh:8080

                      wd4hxg-Sterling.local.mesh:8080

In the end with localnode:8080 entered in the browser

address URL field the browser timed out and displayed
the text you observed in the out take. Not sure why it
changing. If I discover the reason I will post it.

The browser is doing that because it doesn't know the hostname. What IP address does your PC have (with wifi disabled)?

If you want to troubleshoot offline, shoot me an email:  my callsign at arrl.net

Thanks Darryl

I will try another couple of things. Right now I am heading down the

route of reloading 3.0 via tftp. Will see if that works.

Chuck WD4HXG

Spent more time today attempting to restore connectivity to the Titanium (Ubiquiti) M2HP in possession via the LAN Port. I have reset the device several times and the unit still refuses to connect via the LAN Port. Pinging 192.168.1.20 returns the message "Destination Host Unreachable". Also the entry appearing in the wireless table on the Windows box is listed as "MESH" now which makes me believe the unit has reverted to factory defaults as it displayed another test string for the unit after loading the BBHN firmware.

I have tried differing static IP addresses on the Windows box just on the off chance something was amiss there. The SubNet Mask is set to 255.255.255.0.

Any suggestions on establishing communications with the LAN Port?

Chuck

In the ongoing saga I tried to reflash the device but the default address of 192.168.1.20 did not respond to pings nor did browsing to http://localnode:80 work.

In desperation an IP Scanner was used with the IP address 192.168.1.1 responding. The MAC address retrieved matched the device. ???????? Pinging 192.168.1.1 returned a response with response times of less then 1 millisecond. Trying to use the web browser to go to 192.168.1.1 resulted in a time out. I then tried to telnet to 192.168.1.1 and what did appear but a login prompt. I used the default user id "root" and password of "hsmm". Voila! It talked.  The screen below appeared.

So my question now is, where do I go from here if there is anyplace to go?

Chuck

May be making some head way.

I discovered a few nights back that the wireless card was playing in the middle of the conflagration between the device and me. I kept finding a rogue IP Address despite the fact I had switched off the card with the hardware switch. Eventually what I found was the card had to be switched off, then in the network settings if it was showing "Connected"  I had to select "Disconnect". Lastly in the network settings I also had to select "Disable" for the wireless card. Oddly the rogue IP address would change randomly. That stopped once the above was performed. Whatever, dang laptops.

Went back to the device a few minutes ago and could not talk to it via telnet. Checked and the IP was present but refused to ping. <sigh> Took the device down and inspected it closely. Removed the electronics from the case and noticed there is a large surface mount cap near the reset switch which appears to be an afterthought. A close exam showed one end had a nice glob of solder but had not wet the pad so the contact was intermittent. Also noticed the reset switch was touching the edge of the metal end casting. Spent a little time adjusting the fit and now the reset switch seems easier to depress.

Hooked it all back up. ka-ching. Using the ip address and port address of 8080 it hesitated for about 10 seconds and produced a setup screen.  Will repeat and report back later.

Insofar as I can determine, Yes. It arrived in a factory box
with seals. I was hoping the LED's (which are concealed in
the metal enclosure of the bullet and cannot be observed
unless the case is removed) would provide insight into what was
happening. Upon removing the unit I noticed the cap. It
was co-located with the switch but I could not determine
if it was part of the reset switch circuit. Old eyes, etc.

The ends of the cap were globbed with solder. It had
all the outward appearances of a fix for a problem identified
during the production phase. Cap way to large for the pads,
manually reworked, done fast. The reset switch may or may
not have been part of the problem. It just seemed best to
address the potential given the fit. Heap in the chaos of
the laptops, plus operator ignorance and it was almost a
perfect storm.

It appears to me the concept behind the device is if it fails
out of the box, grab another and keep going, then RMA.

One other thing has me scratching the noggin at this time.
I reset the User ID and Password. However when challenged
for it by the device after resetting, the selected password
failed. Thinking I had entered a wrong password I pulled
the connection and then reinserted the cable. It  went to
the 192.168.1.1:8080 address-port combo right away but
upon attempts to log into the SETUP the password challenge
failed again. I pulled the power again and performed the
hardware password reset. Using the defaults it let me right
in. Then went through the reboot after changing the
password and once again it refused to accept the old or
new password. For the short term I just use the defaults
after another reset.

The important thing is to get it up where I have Linksys
units and determine if it is worth the effort to change
over.

I plan to post a write up of the efforts in a single post
which hopefully  will help others avoid some of the
pitfalls I seem to have discovered or created.

Thanks for all the feedback.

Chuckles