Restore compatibility with BBHN 1.1.2

[argilo]

This patch restores compatibility with BBHN 1.1.2. It changes the link quality metric to match BBHN's, and also pulls in a patch that BBHN has made to the OLSRD Secure plugin. I've tested this on my Raspberry Pi, and it's now able to talk to a Bullet M2 running BBHN 1.1.2.

[urlgrey]

Looks good to me. Thank you for taking the time to track this issue down and submit pull-request!

[argilo]

Thanks for merging. I'd suggest creating a new tag and updating the readme (which now suggests checking out v0.4.0). Either that, or just delete the "git checkout tags/v0.4.0" line from the readme and do development on branches, leaving the latest release on master.

[urlgrey]

Great suggestion, I totally agree. I'll update the readme later today.
Thanks again,

--Scott

On Saturday, October 4, 2014, Clayton Smith notifications@github.com
wrote:

Thanks for merging. I'd suggest creating a new tag and updating the readme
(which now suggests checking out v0.4.0). Either that, or just delete the
"git checkout tags/v0.4.0" line from the readme and do development on
branches, leaving the latest release on master.

—
Reply to this email directly or view it on GitHub
#34 (comment).

[chandywerks]

Yeah, you should comment out or update that "git checkout tags/v0.4.0" line.

Is it possible to update if I already have v0.4.0 or do I have to start fresh again?

[urlgrey]

Hi Chris,

I've updated the README.md to not include the tag checkout step. The only
change made to the installation script (install.sh) was the patch that you
made. It's safe to update the project in-place (git pull) so long as there
haven't been substantial changes to the installation script.

--Scott Kidder

On Tue, Oct 21, 2014 at 8:05 PM, Chris Handwerker notifications@github.com
wrote:

Yeah, you should comment out or update that "git checkout tags/v0.4.0"
line.

Is it possible to update if I already have v0.4.0 or do I have to start
fresh again?

—
Reply to this email directly or view it on GitHub
#34 (comment).

[mstyne]

Looks like compatibility has been lost again as of BBHN 3.1.0 ... I haven't been able to investigate further just yet, but symptoms are:

• Linksys BBHN 3.1.0 nodes visible from hsmm-pi powered node
• Node names do not resolve on hsmm-pi powered node
• hsmm-pi powered node is not visible from BBHN-based nodes

73
Mike K2MTS

[Ikata89]

Looks like compatibility has been lost again as of BBHN 3.1.0 ... I haven't been able to investigate further just yet, but symptoms are:

• Linksys BBHN 3.1.0 nodes visible from hsmm-pi powered node
• Node names do not resolve on hsmm-pi powered node
• hsmm-pi powered node is not visible from BBHN-based nodes

73
Mike K2MTS

Is there any solution to this? I'm trying to connect MSMM-PI to BBHN node. The Pi can see the node and connect to it interface, but the BBHN does not see and connect to the Pi.

Any ideas how to fix this?

[mathisono]

The Olsrd release version adopted for this version has moved beyond the version used in the build used in BBHN. http://www.olsr.org/mediawiki/index.php/Main_Page 73 Mathison

…

On Sat, Feb 9, 2019, 5:40 AM Ikata89 ***@***.***> wrote: Looks like compatibility has been lost again as of BBHN 3.1.0 ... I haven't been able to investigate further just yet, but symptoms are: - Linksys BBHN 3.1.0 nodes visible from hsmm-pi powered node - Node names do not resolve on hsmm-pi powered node - hsmm-pi powered node is not visible from BBHN-based nodes 73 Mike K2MTS Is there any solution to this? I'm trying to connect MSMM-PI to BBHN node. The Pi can see the node and connect to it interface, but the BBHN does not see and connect to the Pi. Any ideas how to fix this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlvLKVHksom35x8JuJPvAfqtrPMynMIks5vLs-3gaJpZM4Cqwbl> .