I know that the advice is that we should all use the same mesh name (SSID) but the reality is that different groups have used different SSIDs.  The question then is how do we connect the two meshes with different SSIDs?

I know that the advice is that we should all use the same mesh name (SSID) but the reality is that different groups have used different SSIDs.  The question then is how do we connect the two meshes with different SSIDs?

The .BIN file is for when it is still a OEM router (stock firmware), to upgrade to a mesh node.

You will need to verify you are getting the proper bin file for what exact model you are using (ex WRT54GSv2 vs a WRT54GLv1.1, found ont he label underneath in small print)

If it already has BBHN firmware (or open/dd-wrt), then use the available TRX file, which works across all hardware models ONCE IT IS ALREADY a BBHN node.

So if you were trying to use a BIN file on a mesh node, yes you would get an error. Go download the TRX file and use it on those nodes to update from a previous BBHN version.

I have a "stock" Linksys WRT54G v.4 that I am trying to convert to Hamnet. (Ok, I'm a newbie who bought two units with bbhn installed and also found two others to convert myself)  So far I THINK I have been following the firmware installation instructions.  I selected and downloaded this version of the .bin file:

bbhn-3.1.0-wrt54g-2.4-squashfs.bin

When I logged into the router and started the update process things looked good for a few seconds after clicking "Upgrade".  Unfortunately, I soon received a message indicated firmware upgrade failure.  I have tried multiple times with multiple downloads of the .bin file but never get beyond the failure notice.

I admit I haven't looked extensively through the archives of the forum so if anyone knows of a previous solution or has a solution....probably an obvious error on my part......I sure would appreciate your guidance.

Thanks,

Dave K4DPF

Has anyone collected any metrics on the amount of wan / tunnel / internet activity a node experiences due to just the maintenance and updating of the links? 

I am looking into the support for XW devices from a personal interest standpoint.

OK, for those who still run WRT's, I have added a little widget to the MESH STATUS page that you can download and just copy onto your node(s).

What it does is counts the number of remote nodes and current neighbors and puts a (##) next to the Column header.

For example

This makes it easier to count when you are connected to a tunnel(s) and have lots of remote links. (and YES.... those are actual numbers, just copied from one of my nodes.... MANY tunnels at work here  )

http://www.broadband-hamnet.org/download/applications/mesh

THIS ONE ONLY WORKS ON WRT's ! I have yet to craft it for UBNT. If someone would like to take a shot at it, its only PERL... If you get a copy working on UBNT, email it to me @ Jim@k5ktf.com and Ill get it up here for all.

You would need to copy the file linked above (or the code displayed on screen when you click on the link) into /www/cgi-bin/mesh on your node. Its that simple.

73 & Happy Meshing!

KTF

Here's the math on how IP Addresses are allocated:

bloodhound.aredn.org/products/AREDN/wiki/TechRef/GUI/admin/PerlUI_IP_allocation

... Joe AE6XE

Patrick,

  I found a nice TP-Link 12dbi Omni for $39 + shipping, on eBay, and it works great

73's de Mike wa6fxt

Just a note mentioning that the Ventura County hams are "Meshing" around, also.

73's de Mike wa6fxt

Attachments
 VC_Meshing.jpg [94 KB] :: Ventura County Mesh-Net

A better antenna is a far, far better choice than an amplifier in the majority of cases.

There was some discussion on the AREDN forum at http://www.aredn.org/content/standards (starting at post #14) that may cover this.

Thanks, I also saw the AREDN forum post on this. Is the AirOS version consistent across all
Airmax M products of the same hardware version i.e.for XM or XW?

If it's possible to get serial number correlation between old and new devices, a co-operative
distributer could check against their stock before shipping; maybe not all of their units, but
enough to indicate what's coming (or to not ship). It's an option to just go ahead and order and
hope for the best either way, knowing that newer versions will be supported sometime soon
though it may not work out for immediate needs.

I'm not suggesting people post exact S/Ns but if we can figure out a range/pattern...

Dave

I hope to have two nodes up here (fn20hd) in the next few weeks. Who else in the Philly area has nodes running and where are you located?  Did you add your node to the map??

--Ed

Cool, thanks Wil! It looks like I'll need one with an rp-tnc connector. I heard that there is a lot of loss associated with the coaxial cables... Should I just try to find one with the shortest coax? 

Douglas, yeah I'd definitely like to be on the list. I'll shoot you an email.