To avoid paragraphs being crunched, click "post reply" rather than typing inside the quick reply box.

This also gives you a preview button to see what it will look like before you click submit. Be sure and click only one time, giving time for the server to handle your request.

With regard to a specific build of any HSMM-MESH or Broadband-Hamnet firmware for Raspberry Pi, Pi 2 or Beaglebone black, No version has ever been released.

Talented users have taken each operating system, added the OLSR features and the DNS processes, and done one-off conversions of each of these models. It appears that plenty of horsepower exists even in the Pi Zero to do the same thing.

We don't advocate the Pi or Beaglebone directly serving as a node for several reasons. First, it is not water tight and would need to be in contact with a USB or Ethernet connected access point located high enough to be useful. This presents some problems as you would normally like to have a really strong signal on the node that serves your BeagleBone, PI, etc. such that hop count to that node is very low.

Second, If your mini computer lives up to its abilities, you will be serving up web pages, possibly hosting a file/FTP store, APRS and, running Asterisk and possibly one or more chat server programs. Others add Tickets CAD and locally stored Open Streetmaps to the mix to manage your deployed resources. As you stack more tasks on to the quite capable mini computer, you take away cycles from near real time tasks like Asterisk, decreasing the concurrent call count that can be handled with quality audio.

In addition, 5v power over Ethernet (POE) is even less standard than the 12v used in many setups. It does not port well over a distance due to 5v needing to be not more or less than 5v. Other power is 12v or higher for the Ubiquiti and IP phones, so starting over with voltage doesn't hurt you on short runs and still works fine as the length of your CAT5 grows. It is quite easy to have a solid 5v power source for the Pi/Bone at your operating position and leave the higher power/better antenna job to a POE connected Ubiquity mounted above your head. With native water sealing and POE already handled, it's a snap. Such a host, acting as a mesh node with direct LAN addressing and hard wired to the Pi/Bone and will get premium service to each user.

Nothing here says you CAN'T make the Pi/Bone your mesh node, but why fight all of the above factors just to do it?

Restating the current situation: Broadband-Hamnet does not offer any builds of firmware now or in the past that directly convert any model of Beaglebone or Raspberry Pi to BBHN operation. Users are free to whip up one and share the recipe with others. Our recommendation is to have a dedicated mesh node hard wired to the mini computer over CAT5 cable and give it a solid 5v supply in an area where weather protection is not an issue.

Dear Members,

Way back in the version 1.0 days there was a way to load the BBHN 1.0 software on

a Raspberry Pi and use it as a BBHN Node...  Has that process expanded to version

3.1 and if so... Where do I find it???

The reason I want it is I want to build a mobile BBHN Node for my car... and I want to

be able to expand the BBHN in places where using a Raspberry Pi could be advantageous.

Any suggestions much appreciated.

73 Dave WA5DJJ

Dear Members,

Way back in the version 1.0 days there was a way to load the BBHN 1.0 software on

a Raspberry Pi and use it as a BBHN Node...  Has that process expanded to version

3.1 and if so... Where do I find it???

The reason I want it is I want to build a mobile BBHN Node for my car... and I want to

be able to expand the BBHN in places where using a Raspberry Pi could be advantageous.

Any suggestions much appreciated.

73 Dave WA5DJJ

Dear Members,

Way back in the version 1.0 days there was a way to load the BBHN 1.0 software on

a Raspberry Pi and use it as a BBHN Node...  Has that process expanded to version

3.1 and if so... Where do I find it???

The reason I want it is I want to build a mobile BBHN Node for my car... and I want to

be able to expand the BBHN in places where using a Raspberry Pi could be advantageous.

Any suggestions much appreciated.

73 Dave WA5DJJ

Thanks for getting this discussion started, Robert.

For about two years I've had a node running in Berthoud.  Usually, I have a Team Talk 4 server connected, but the node is always on the air and everyone is welcome to connect.

73, Jay    W0AIR

We're having a BBHN Mesh discussion at the NCARC Hamfest in Loveland, CO on Saturday, January 23, 2016.  Forum runs from 10:00 to 11:00. 

Details:  http://ncarc.net/?q=node/290     or see menu at  http://ncarc.net

73, Jay W0AIR

That sounds much like a problem that another user experienced the other week.

We will for sure get you set on the right stock firmware first and then hopefully back on track:

1. View videos: here and here
2. Download your suitable TFTP client here.
3. Download UBNT v5.5.x firmware here.
4. Following the methods in the two videos (mileage may vary) and your TFTP client, and
5. TFTP the stock UBNT firmware back to the NanoStation M2.
6. Once fully booted and re-setup using stock firmware, try re-flashing the unit back to BBHN

Let me know if you have any questions and please let me know the outcome either way. And then, we will see how to proceed from there. Thanks!

I have 5 NanoStation M5's, all I did was make certain they were XM versions before purchasing.  Flashed with BBHN with no problems.

Decided to include the NS M2 to my equipment collection; did the same... verified it was "XM".  Sadly I didn't look to see what version of factory firmware was already installed; made the mistake of using my M5 experience - just looking that the firmware version started with XM.

I reflashed with the BBHN 3.1 for the NanoStation M2; it went through all right; and then got the "NoCall" page. But when attempting to   change the call or password... the Save function errors.  Also, cannot reload any other flash; get a message "file type  not recognized".

I then went back to the main NoCall page, and in the lower right corner noticed something strange:

screen-shot (look at the flash free space value):

http://www.tim-yvonne.com/ham/temp/BOOTLODR.JPG

does this point to being the announced bootloader problem ?

Honestly, I am not aware of the reason why the whole post was removed (EDIT:  I should have read your edit more carefully. You removed your main post.  I thought your original post was deleted and you opened a new topic under the same name). However, from looking at my email log, one person said that your problem possibly stemmed from this: https://wiki.openwrt.org/toh/ubiquiti/airmaxm

Your pictures were hard to read on this forum, so I had to download them to figure out what you did (luckly I still had the pictures). What is came down to is that you serial consoled into the router, turned on TFTP via the serial console (details here (ubnt website). Summary: Type "urescue" at serial prompt), grabbed AirOS XM 5.5.11 from the ubnt website, put the router in TFTP mode and TFTP'd the firmware back to the UBNT device. And then after the node fully flashed back to the origional (and older) stock firmware you proceeded to install BBHN onto the node. Does that sound right?

So for archival purposes (should anyone else have the same problem and need to search for it): "I flashed a bullet m2 hp today with 3.1.0 and when I tried to setup the mesh node it kept giving me an error. I telnet into the device and find out there is no available space. Tried to put the m2 in tftp mode and can't even connect to it. Any advice?" -KE5EUA  (Edit:  Since you deleted your original post, let me know if you want this quote removed since you have full ownership of it.)

I think KG6JEI's earlier comment is still valid.  It is pretty hard to beat the price of a Ubiquiti PicoStation... (<$80) and there is "no assembly required." And, if you want a 60º sector with MIMO you absolutely cannot beat a 2.4 or 5gHz NanoStationM2/M5 at just $5 to $10 more. (Personally, I'd avoid the NanoStation loco unless range is not an issue.)