http://ae5ca.com/?p=74

Summary: Ubiquiti NanoStations are a better choice, generally.

If you are wanting to build a mesh in your house, the 54G's are fine.    If you are looking to have an externally mounted node, you can't beat the Bullet for simplicity and ease of placement.

Also, I'm running a Bullet M2 with a $3 passive POE injector I bought off of ebay.   It's running fine off of 12 volts (my Travel Trailer's main battery) and I'm powering it through about 40-50 feet of cable.  I suppose if I needed to go with a longer cable, I would need the nice 24V injector.   I don't use it for hsmm-mesh (Yet), but I use it to pull in the campground wifi with a high gain co-linear antenna.  (A necessary evil to work on the road)

I'm also new here and I'm asking myself some of the same questions. I can only speculate but part of the idea may be to keep out the riffraff. It may also be to leverage whatever credibility ham radio was when it comes to installing nodes on towers, etc. I think the AREDEN folks have fully committed to that concept.

Seems BBHN is several part put together:

Linux computer (open-WRT)

wifi radio

OLSR

Web server

Web page user interface

cron job to send callsign

Someone has already published how to do this with a raspberry pi (HSMM-PI). I'd really like to learn to do it with these $20 travel routers or the $30 ones with built-in batteries.

  - Tom

I have a Ubiquiti Titanium that BBHN 3.1.0 was uploaded. Upon trying to save the Username and Password the browser displays the changes were not save. Attempts to just save just the Password also return a notice the changes were not saved.

Attempts to upload another copy of 3.1.0 fail with the notice the file is not recognized. In an effort to start back at Ground Zero an attempt was made to reload the Ubiquiti firmware using the interface within BBHN in the admin screen. This failed also with the message the file is not recognized.

Reverting to Windows TFTP attempts were made to upload the Ubiquiti firmware. The command line syntax used was:

                        tftp -i  192.168.1.20 put TI.v5.6.2.27929.150716.1134.bin

TFTP was invoked while in the F: drive so the filename was only specified. The following was the result apparently after about a two minute timeout. I tried specifying the file to transfer by prefacing the filename with "F:" and also "F:\".  I can ping 192.168.1.20 and receive a reply when the device is in TFTP mode (holding the reset button for 25 seconds until the LED's alternately blink)

Can someone tell me if the syntax used for TFTP is correct?

I am trying to setup Asterisk on RPi2, the node see it. I set it up, but once I get to see the mesh status, there is no advertised listed for this device. What am I doing wrong.

I have a Rocket M900,

I have been trying to get it to work between 2 of my homes about 2 miles apart un sucessfully.

Heres the question, If I flash to mesh firm ware will this in anyway improve my signal, IE more watts ETC?

and where the hell is the spell check feature on this site ?????

I have 3 nodes  wrt54GL nodes on my mesh. They talk togeather fine and I was looking for a way to link them to my local LAN.

I took one node and setup the WAN address and set it as the mesh gateway. From my LAN I can connect to that node and view the admin/status page, but I cant reach any of the other nodes.  I have tried using IP address only. How do I tell mesh nodes who  in the mesh is the gateway?

I have 3 nodes  wrt54GL nodes on my mesh. They talk togeather fine and I was looking for a way to link them to my local LAN.

I took one node and setup the WAN address and set it as the mesh gateway. From my LAN I can connect to that node and view the admin/status page, but I cant reach any of the other nodes.  I have tried using IP address only. How do I tell mesh nodes who  in the mesh is the gateway?

Well here is another tale of Ubiquiti woe.  I flashed another device and the upload went as expected. After upload and returning to localnode:8080 I am challenged for login credentials. Used "root" and "hsmm", all lower case. Status screen is displayed. Clicking on "Setup" takes me to the page for entering the new node name and new password. Entered new node name and password and click "Save". The little whirly wheel rotates a few dozen times and then the screen flashes with the message the name and password were not saved.

See below:

It also states the password must be changed during the initial configuration. OK?

I can enter the "Administration" page and setup to upload the firmware in an effort to upload a fresh copy of the firmware in the event the initial copy was corrupted somehow. However this attempt is thwarted as the firmware queued for upload is deemed "invalid". Initially a fresh download was tried. When that did not work the first copy downloaded was queued up and the same error message was displayed when clicking on upload.

Any obvious faux pas?

ok I'm in, thanks everyone for the help

Rick

Ping 192.168.1.1 and see if you get a reply. If so then try typing 192.168.1.1:8080 into the url field. If the page flashes a message it is redirecting and does not continue then click on the highlighted link.

Thanks,

My computer does not have a wireless card in it, nor is their anything showing up as wireless on the computer, Im assumeing that I do not have one.

I also now have my rocket M900 pluged directly into my computer, and I'm not going thru my router.

when I release, flush dns and renew the IP address, it get the system timed out error message?

and ctrl=F5 did not seem to do anything ?

HELP

After confirming that your computer's wireless interface is disabled/not connect to any router....

Clear your browser cache after doing the initial config.

Firefox:
  On Mac OSX: CMD-R to do a hard refresh on the page
  On Win: CTRL-F5

sorry for the repost the forum server laged