Peter,

I totally get it... and we have discussed this issue recently.  Unfortunately it's not here yet.  Thanks for your thoughts on the subject and we hope to be able to include such a feature in the future.

Andre, K6AH

Well not 50 that was as an example, but we have about 10 nodes up now on one side of the valley and are slowly building around the valley. Problem is some nodes are managed by the same OP who got permission to be at some QTH's tower. I'm sure the owner of the QTH doesn't want to be bothered with "CAN YOU UPGRADE MY NODE" requests so if a Op has 5 or 6 of these sites, it becomes a pain to drive out and upgrade. I thought possibly it could be done remotely by upgrading the furthest point out first but after reading the threads it seems that is not possible as the unit defaults to an access point. Maybe that is something that can be discussed for future versions. I see these networks getting larger and larger with the release of 5.8Ghz and 3.4Ghz nodes and at some point upgrading would be nice.

THANKS FOR THE QUICK REPLY!

73 de KF7PSM Peter

Is there a file somewhere that shows what changes where made between versions? I don't understand why version 1.1.x is not compatible with 1.0.x?? I did a test upgrade and all of a sudden the 1.0.x nodes disappeared? There is no backward compatability?  I don't understand why there is no compatability, did OLSR change or some other underlying way traffic is passed? A CHANGELOG would be nice as well as some kind of FAQ.

This is potentially painful for larger networks. Is there a FAQ or Doc on how to upgrade a network say with 25 or 50 nodes? Would you have to travel to each node site and do one bye one or can you perform upgrades over the mesh with the farthest points first working your way back? From what I've read in past posts it seems you have to be at the site or at least in wifi range to get to the node you are upgrading with a .trx file?!

73 de KF7PSM

It might be better to start a new thread with your questions as they are not related to the original posters Inquiry. It helps keep the forum clean and easier to find information.

Is there a file somewhere that shows what changes where made between versions? I don't understand why version 1.1.x is not compatible with 1.0.x?? I did a test upgrade and all of a sudden the 1.0.x nodes disappeared? There is no backward compatability? This is aweful for larger networks. Is there a FAQ or Doc on how to upgrade a network say with 25 or 50 nodes? Would you have to travel to each node site and do one bye one or can you perform upgrades over the mesh with the farthest points first working your way back? I don't understand why there is no compatability, did OLSR change or some other underlying way traffic is passed? A CHANGELOG would be nice as well as some kind of FAQ.

73 de KF7PSM

Hi! The node is on the roof of a building near King William and Mary streets, about 60 feet high. It has a dish pointed almost due east, and a 15db omni. Both are vertical polarity.

I've run link models using Radio Mobile Online, and it tells me a link from LaSalle Park is possible. I've been able to establish a weak link from the Bridgeview parking lot, across from the golf course near Hwy. 6 and Plains rd, using a 12db yagi.

I'd love to hear how you make out. If you can, try a link from the top of Kern's road. There's a parking area about halfway up to Hwy. 5 that has a great view of dowtown Hamilton. Send me a screen shot of the Mesh Status page, we can call it a QSL card. If you get a good link (>50% LQ) don't forget to sign the Hamchat 'guest book'.

The longest link I've established is a little over 10km to the Devil's Punchbowl in Stoney Creek. The downtown node's site is problematic; a lot of building clutter, and a -75dbm noise floor.

The node is running V1.0 and won't be upgraded until I take it down in a few weeks.

I just had a somewhat similar experience loading the latest BBHN 1.1.1 to a brand new Bullet2-H with AirOS v 4.0.2.  When I began the upload process I immediately got an error message at the top of the AirOS web page "Uploaded configuration file is too big.  Maximum allowed size is 65535 bytes"  What...65535 bytes?  Did something change in the new Bullet2-H...or did I get the wrong Bullet?  I can easily return this Bullet if it is the wrong thing, but I'll need to know exactly what Bullet model is the right one for BBHN.

Thanks, Bill, N4SV

Version 1.1.1 has been released to resolve this issue and can be downloaded from the software download page.

Congratulations you found a bug.

The build had a significant amount of testing and tweaking and retesting and tweaking and retesting but this one slipped through.

Thank you for the report.  I will provide updated info as soon as I have it for you.

All of us in North Texas will bow to your feet.

You have to beg and plead and send money to the webmaster, acknowledging his greatness, using words like Your Lordship, and Oh Master of the Universe.

Naaaa...

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-topiclist/forum-44-dentonnorth-tx.html

Enjoy !

What process do we need to follow to request a regional forum for Denton County, TX? We are a young group to BBHN and I know many of our members will be looking for a place to communicate on a forum. Several have expressed interest in a Google Group or Yahoo Group but I would prefer to keep it in an area where more people have knowledge on the subject.

Thank you,

Eric Gildersleeve KD7CAO

President, Denton County Amateur Radio Association (W5NGU)

Hi all,

Well....I have been working with BBHN v1.0 for the past months and had figured out how to integrate DD-WRT OLSR mesh nodes into our network alongside the BBHN mesh nodes running v1.0. While I still had a few bugs to work out (like hostnames and OLSR config pages on the mesh) they worked quite well and played nicely with BBHN v1.0. This morning I test loaded V1.1 on my main mesh router and immediately broke my access to the DD-WRT mesh routers.

My first thought was that OLSR Secure had been reinstated in this version, so I logged in to turn that back off. My SSID is still set for BroadbandHamnet-v1 (instead of the new default -v2). However, there is obviously something more that makes it incompatible, as they still failed to talk to each other anymore.

So, I guess this begs a couple questions. What else has changed that would break the compatibility with v1.0? I am also curious if anyone has given thought to creating a version of firmware that would fit on the newer WRT54 and other routers with limited space? DD-WRT opened up a HUGE variety of router options for running mesh networks....and now that compatibility is broken again.

73, Ken KD6PGI