Please confirm:

• All are on the same release (e.g. BBHN 1.1.x)
• All use the default SSID
• None are Ethernet-connected to each other (the only network they share is the RF Mesh)
• You haven't modified the OLSR Secure key
• The Linksys nodes haven't decided to mesh on a channel other than 1

Andre, K6AH

I have two Linksys WRT54G's that "see" each other on the mesh.  Today I flashed a Ubiquiti Bullet that I can access with no apparent problem.  However it doesn't "see" the Linksys units and they don't detect it's activity.  All units are on channel one........any thoughts about where I went wrong.

I'm new to HSMM so presume it's operator error.

TNX,

David Reid W6KL

Burbank, Calif.

All,  I've been looking at the Link Quality (LQ) and Estimated Transmission Count (ETX) values and finding they don't seem to be representative of "common understanding" reality and don't compare to, for example, the results from a ping.   Granted, this issue may not be a problem as the current #s may work perfectly fine to calculate the best routing paths.  But it bugs me.  Here's a write up of my investigation to tune olsrd parameters in case this bugs you as well.  

The source code of olsrd is using a weighted exponential moving average.   The default olsrd parameter for this weighting is "HysScaling" and a value of "0.5".  The default HelloInterval is 2 seconds.  

This translates to a weighting that only makes significant (~98%) the last 6 packets in 12 seconds to base route decisions on.   The most recently received HELLO packet, if missed, would instantly drop the LQ down 50%, 2 missing in a row, down 75% and close to the threshold to drop the node out of the route table.

The weighting looks like this (add up the values for which of the last 6 hello packets were received to determine LQ):

I'm putting in a HysScaling value of "0.1" to see if LQ and ETX values are better representative.   The 0.5 value may be better for mobile nodes with dynamic environments to better compensate.  But our nodes here in Southern CA are fixed based and LQ should not change so rapidly.   For a weight scaler of "0.1" the route decision (~98%) would be based on the prior 40 packets over 80 seconds.  The first 6 look like this (smoothing further over time):

The weighting value is determined =x(1-x)^i, where x=HysScaling value 0>1, and i is 0, 1,...

This is the theory.  Feel free to shot holes in this, I'd rather not be going down a bogus path and not know it...

Joe AE6XE

Hello again,

There is a connection to DHCP with this issue after all. I tried an older Dell laptop with a 3COM NIC and it will not get an IP address even though my other laptop does. I have also tried using static IPs and gateways, this allows me to get to everything on the network (including SSH to localnode) except to http://localnode:8080. I reverted the N6SER-100 node back to the v1.0.0 firmware and all the issues are gone, even with the older Dell laptop.

I have reverted all my nodes now to v1.0.0 of the firmware and I am sure the cause of this issue will be found. If I can help in anyway let me know.

Thank you all for the development of HSMM and the support.

73, -Dan

Hi Conrad,

Thanks for the reply. Yes, I am getting an IP address via DHCP. I have also now verified the /etc/config/firewall settings. They are the same on both nodes.

73, -Dan

Great info thanks VE3RRD

Bob Morton VE3BFM/VE3WY (near Everett) sells a couple of versions of omni antennas and a high gain yagi (with weather shroud). Although I don't see them listed on his website, he does stock them: http://mapleleafcom.com/ . Bob also sells the required LMR240 jumper (RP-TNC to N) which he can make up to your required length. You can also order the TP-LINK 24dBi Grid Parabolic (TL-ANT2424B) from Staples online: http://www.staples.ca/en/TP-LINK-24GHz-24dBi-Grid-Parabolic-Antenna-TL-ANT2424B/product_142246_2-CA_1_20001 or from "The Source" online: http://www.thesource.ca/estore/product.aspx?language=en-ca&catalog=online&category=Outdoor%20Antennas&product=8006116 73, AL VE3RRD

Updated to the 1.1.0 firmware on my mesh - multiple nodes both ubiquiti and linksys..

In 1.0.0, I had been utilizing laptops with Linux and OLSRD - this allows both extension of the mesh as well as access to web tools like trivnetdb, etc - directly from a laptop rather than having to pair each laptop up with a WRT router or whatnot.   Also quite useful to temporarily bridge an isolated BBHN mesh to the internet via a USB 3G phone or equivalent. 

In the new firmware olsrd on a laptop complains that all packets from the mesh are insane... :-)

[ENC]Rejecting packet from 10.118.205.197
[ENC]Packet not sane!

Has anyone else had this issue?   This is after modeling the config file after the BBHN configuration including the olsrd_secure_key

For interoperability with other BBHN nodes I would rather not turn off the secure plugin, although it might be tempting if no solution eventually presents itself.  

I thought this might be related to time synchronization but that appears to be ok.  

Any suggestions?

When plugged into N6SER are you receiving an IP address ?

You may be hitting the issue being described http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-3-firmware/topic-1038-v10x-to-v112-one-pc-discovered-other-not.html#ccbp4636

I have the simple network shown in the attached picture. The N6SER-100 node is a WRT54G v2 and my node, WA6PZB-100 is a WRT54GS v2. The issue is that while I am connected to the LAN port on N6SER-100 with the PC, I cannot view the status page either via localnode:8080 or N6SER-100:8080 or via any of the combinations of FQDN and IP address URLs. However I can access N6SER-100 from the PC connected to the LAN port of the WA6PZB-100 node. I can ping localnode on the PC connected to N6SER-100 and can even SSH to it via the LAN port. Very weird, I did not have this issue with v1.0.0  firmware.

Attachments
 mesh.jpg [53 KB] :: Diagram

For reference in case it turns out to be on our side:

What were the other 5 nodes you said you had issue with ? (Type and version of hardware)

Hi,

  Just noticed that BBHN just release version 1.1.2.  What are the release notes for the upgrade from v1.1.1?

--73 de N1OBU (Doug)(FN41AN)

A laptop doesn't need to be running OLSR to participate. 

You can hard wire in or put an access point in to move the traffic off the ham band into the part 15 band allowing local users to gain access without advanced configuration and allowing the mesh channel to not receive unneeded local interference.