I tried to enter the details for the bug, but the Website logged me out before I could save it.

Since I could not mouse the text into this window, I am attaching a description as an attachment instead.

Since I don't see any indication of it after uploading it (as a text file), please contact me directly if you do not receive it.

Thank-you.

de Vern (W6NCT)

I am not seeing an attachment on my side either.

If I understand the concern correctly (node with a path one way show as  a neighbor ). This sounds correct behavior to me.

The node is indeed a neighbor (as defined by our routing service olsrd). It is a neighbor with a 1 directional path.  Currently the software will not use such a route however it does keep track of it as a neighbor it can hear and could possibly become a bi directional neighbor if the RF path changed.

If you first click POST REPLY it opens an editor window which more formatting features... and it's WYSIWYG with a preview feature.

Andre, K6AH

What sort of hardware is Node S?  Without that we are just taking shots in the dark.

"Node-850's Mesh Status indicated Current Neighbors to be Node-101, Node-851, and Node-S; but No Remote Nodes. I was under the impression.... was under the impression that this meant that Node-850 could talk (directly and bi-directionally)" This does not necessarily mean the connection is bi directional., just that Node-850 can see packets from Node-S. 

Ubiquiti hardware has a better receiver, it is very possible that even without any noise from wifi devices that Node-850 can see Node-S's beacons even if it can't establish a bidirectional iink,  This would show up as having an LQ value in the Mesh Status screen, you would need to look at the OLSR Status to see if its bi directional or not.

"but could communicate indirectly (yet bi-directionally) to Node-101 and Node-851 (i.e., via Node-850). Correct?"  Generally true, of course its possible contact may not be possible if a link in the path is overloaded, or a high ETX path.  An single hop ETX of 2.0 means a 50% chance the packet won't make it . A ETX of 4 is up to 75% chance of loss on round trip.  LQ can be high in one direction and very low in another direction. (one way UDP streams wouldn't have an issue with this for example)

" To test the connection status ambiguity, we powered OFF Node-850; everything else remained the same, physically and operationally. After a delay, we got the following... --- Node-S's Mesh Status indicated NO Current Neighbors and NO Remote Nodes. I was under the impression that this meant that Node-S couldn't really talk (directly and bi-directionally) to either Node-101 or Node-851"

This makes sense if its a VERY low connection (very low LQ -- You don't specify ) which your getting a lot of feed from node 850, and just enough from Node S to know its there. There is some level of bidirectional required for everything to exchange correctly at the low levels  (olsr secure attack prevention code) to get name data, and to exchange some keys. It may be that the traffic is going via 850 for the majority and were just seeing the beacons and able to correctly decode them with the additional data provided via 850.

An output of telnet localnode 2006  and a copy of your olsr status all page may provide some additional details rather than us taking guesses.

"I don't quite understand why Node-S' Mesh Status included itself as a Current Neighbor (?); perhaps you can explain that (i.e., separate from the primary issue/concerns below)."

I didn't see that in your initial inquiry , the output of the above data would also help on this one as well to see what is going on.

[Posted wit Post A Reply, this time; as opposed to Quick Response] [Cut/Past no longer works for me, which make typing much slower]

Hi Conrad (KG6JEI),

I'm pretty sure that Node-S is a Bullet; and at the time of the test, it may have been using a 24 dBi directional (screen-dish type) antenna.  I'll have to check with its owner to be sure about the antenna, as it is not my node, and he was making configuration changes a couple days prior to our test.

LQ values weren't constant or even very stable; but were typically in the 63-100% range at the times that I noted them in this test sequence.  Node-S indicated Node-850 at 100%, with Remote Node-101 ETX=3.12 and Node-851 ETX=2.97.  One of the captures I have for Node-850 shows Node-101 at LQ=82%, Node-851 at LQ=68% (even though they were next to each other), and Node-S at LQ=63%.  Other evidence seemed to indicate that the two bullet nodes may have been de-sensing each other a little (e.g., numbers improved when I moved them farther apart, and when I turned off one of them). 

Thank-you for the extra information, I'll try to capture more statuses the next time I test there.  Hopefully that will paint a more complete picture.

Is there any document to tell us how to read the OLSR status screens, and how to interpret ETX and LQ information?  There is so much information on the Web-site I haven't found it yet.

I was unaware that I could telnet to the other nodes, thus far, I have only been selecting the other nodes via the Mesh Status, then traversing their menus.  Is that functionally the same?

Thanks again for the info.  Next time I go up to test, I'll try to get more screen captures.

de Vern (W6NCT)

Sorry, after re-reading my last reply... it was a little terse.  We are working on an upgrade of the BBHN web services and expect the upgrade to be much improved... including searches of the Forum.  In light of this, and the fact that we didn't write it, it's difficult to justify even looking into the current editor.

Others seem to have gotten around issues with it, so if it continues to frustrate you, then perhaps using another editor would save some of the aggravation.

73,

Andre, K6AH