@ZL1CQO - Truncated data... It took a few reboots of all my nodes to flush it all out as it seemed to be passed around, back and forth. No worries! :) This is what happens when we experiment!

That and I have one node that is kind of cramped for memory - and THAT is the one that gets flaky first before anything else goes wrong.  So it is the one I keep an eye on the most.  It's so constipated it wont let the HamChat application write anything to memory anymore...  LOL

Mental note - 60KB of flash memory isn't enough for a WRT54GS to be healthy and happy...  :)

Bill - N5MBM

Sorry :-)

Was there any indication on what was affecting Olsrd?

jon

AHA!  I found the culprit...  I got corrupted data from a RasberryPi node undergoing testing and experimentation having its .conf files being edited...  And of course my nodes passed this bad data along to other nodes... 

My apologies to those nodes that got the cancer...  Everything is stable again now!  (fingers crossed)

It took rebooting a bunch of routers to make it all go away but its working now!

A note to all the guys I tunnel with - let me know when things get hinky!  :)

Thanks for giving me a clue as to where to look!

Bill - N5MBM

Send me an email to KF7MCF@hotmail.com to get put on the news list, we just did a test from one of our Valley Hub sites today... We are using 2.4Ghz and 5.8Ghz links. We just went half way across the valley with a connection that sends two way streaming audio and video.

In our latest usage, (the Served Agency being the Boy Scouts for the Scouting for food Drive), we lit up 1/4 of the Salt Lake Valley (an area about 8 miles by 8 miles) with 13 nodes tying into a Valley Hub Site.  We used TeamTalk to send live streaming video and audio of what was happening from sites around the valley to the BSA Headquarters in Salt Lake City. 

You can read a report of the event on this site at:

HSMM-MESH Info/Usage Articles/Scouting for Food

David T. Bauman

KF7MCF

If you are using bbhn-3.1.0 then you can use the VTUN tunneling described at: http://www.broadband-hamnet.org/documentation/204-the-tunnel.html 

You can find the bbhn-3.0.1 TRX file to update a Linksys node at: http://ve3wex.ddns.net/wax/files/bbhn-3.0.1-brcm-2.4-squashfs.zip 

The procedure to turn on DTDLink for connecting co-located Linksys nodes (via external switch) is at: http://ve3wex.ddns.net/wax/files/How to enable DTDLINK on a Linksys Router.pdf 

I have a Ubiquiti Nanostation M2. Yesterday, I noticed there was a firmware update available. Today, I tried to click refresh so I could download it using the administration tab, it failed.

The following error was noted:

Downloading firmware list...
Connecting to broadband-hamnet.org (71.42.236.91:80)
wget: server returned error: HTTP/1.1 404 Not Found

my node has internet access.

Any ideas?

It seems we have a conflict here... whether or not to use one or the other... BBHN is trying really hard to tell everyone by PM not to use AREDN and to consider them as spam and they're also telling us there will be legal actions to prevent AREDN from moving forward... With that said, I'm am at odds because I can see both Dev teams able to contribute to the MESH effort. Both are operating under the GPL by using OpenWRT. So the squabbling must STOP NOW!

Both teams must come up with some sort of memorandum of understanding to keep the MESH project moving forward. We need complete standards to work with. The Linux community already does this with the GPL, so if either one of the teams cannot play fair under the GPL, then the efforts of the MESH project stops. I don't want to see this happen. BBHN and AREDN need to work together... PERIOD!!! Figure it out people! I don't like making choices because it causes a disconnect for the MESH project.

BBHN is NOT going anywhere so AREDN must put differences aside and find a way to work with BBHN and vice-versa! I will be putting the same message on their forum as well... I'm not the only one that feels this way, I'm getting all kinds of PMs and emails telling me the same thing... STOP THE SQUABBLING!!! START WORKING TOGETHER!!!

Thank you and 73,

Tim Gelvin, K3TEG
ARES Emergency Coordinator
Northumberland County, PA

I have also managed to get this working.

What I have found is:

Changing settings in the hsmm-Pi interface and saving will overwrite the Olsrd.conf file

I had to change the broadcast address in Olsrd.conf to 255.255.255.255

The vtund.conf file was pretty straight forward and just needed the relevant IPs working out for client & server based on the network address used.

The only issue I now have is that the Hsmm-Pi web interface sometimes doesn't like scrolling. I have a short mesh neighbours list and a long list of services that extends off the page.

Good evening,

I got an email about the other site. I decided to come here and saw your post. What is going on?

Mike AE4ML

The next time it craters - I will try it...  It keeps crashing - and then will be stable for weeks!  The other day it crashed 33 times in less than 24 hours...  Now it's been happy.  Before that it had been running close to a month without a reboot...?...  Which makes me wonder...

Are some of the nodes tunneled in feeding me corrupted data or what...?

I will try that the next time it crashes...

Bill - N5MBM

Ok, something weird is going on. The domain names b b h n d e v . o r g and a r e d n . o r g were mysteriously deleted from my post.

As Bob Dylan sang... Because something is happening here But you don’t know what it is

Hey guys,

I have two WRT54G v2's for sale if anyone is interested.

$15/each + shipping.

I will preload BBHN 3.0.1 or DD-WRT on them if you want.

Email me if interested.  my callsign @ arrl.net

Bill, can you run 'olsrd' manually and collect the output? It may have some messages that would be helpful.  I've seen similar when the olsrd.conf file, in /tmp, has been edited and has errors in it.

        -Rusty-

Ok, I am confused. First I see that there is a new version of the bbhn software, 3.1.0, but the release notes on the software download page are still for 3.0.0.

Then when I go to b******.org to see if the release notes are there, I find the site is now a******** and the statement Recently, the developers of BBHN software have kicked-off a new project focused on taking this technology to the next level 

So, it looks like there are now two separate projects, bbhn and ardent. At this point, and based on the little information I can find, they are still pretty much the same. But., presumably going forward they will begin to differ. Will they remain compatible (I.e. will they inter-operate)?

Is this split (if that is what this is) between the former bbhn developers good for the ham meshnet community, or?

Any answers or even speculation welcomed.

I solved my problem. Turns out I had mixed case names in the vtun config file. Solving that, I am now able to establish a tunnel from my Raspberry Pi HSMM-PI node to my BBHN 3.0.1 node. 

In the last few days I have had to reset my routers because the OLSR got corrupted or crashed over 33 times in less than 24 hours - multiple times... (YIKES!)

Now...  How do I troubleshoot this and give the developers some useful information to figure out what is wrong?

Now that I have it loaded - it's coughing and I am trying to figure out what to do about it! :)

Bill - N5MBM

www.n5mbm.net