I have an Ubiquity Nano setup with firmware 1.0.1. I can go to localnode:8080 without issue. When I click on the mesh status, sometimes node names are displayed and sometimes just the IP is displayed. When just the IP is displayed I am not able to see any remote nodes and the neighbors are nodes that I should not be able to connect to directly. The only node I should be directly connected to is showing up as a remote node, when it does show up. If I click on any node I am not able to go to that node.

I have tried rebooting and even reflashed the firmware on the Nano. This did not resolve the issue. I have tried various things on my box including flushing the cache, restarting the browsers, and even rebooting the box.

I have attached a small screen shot showing the name / IP issue.

Any advice on resolving this issue would be greatly appreciated.

Attachments
 QTH Mesh Status 1 sm.png [12 KB]
 QTH Mesh Status 3 sm.png [10 KB]
 QTH Mesh Status 2 sm.png [5 KB]

The first thing I see is 2 nodes with zero LQ. This means we have absolutely no good connection to them.

My first question would be what devices each ip is  and what  version firmware they are and how far away they are.

Secondly, the receivers and  antenna have been reported to be better on the nano than a Linksys by the beta team members,  expect to see nodes you use to not be able to see.  

The one with 89 should have a high enough link to exchange names given enough time (not sure if you just started it)  

I don't see where you show the remote node part showing up in the photo.

If you could provide this feedback it will give us a start.

The symptoms you describe sound a lot like an antenna aiming issue (not knowing who is in what path there)

I've worked with Clint and I know those OHC nodes were just upgraded last Sunday so this may be why your seeing them better now. Maybe other changes were done to the other nodes your speaking of as well.

SM1 and SM2: These show you have a reasonable connection ( 83-89% to OHC-168 31-41% to the OHC-OMNI and 42-52% on KF5NEP) I also note that as the OHC-OMNI went up the KF5NEP went down which may either be atmospheric or an antenna direction change.

SM3: For the first and third node this is EXACTLY as expected, names will NOT show up when the quality is so low.  the 2nd node is a bit more interesting in that it shows but doesn't have a name  and the link hasn't fully established. This photo actually looks like the node has just rebooted and is still syncing up and hasn't received the remote node list yet (takes a little bit of time)

Keep an eye on the RED led on the nano --- This led is illuminated when you have a connection established.

You may want to look and see if the node is rebooting after you log into it (you would see the uptime resetting) this could happen with a bad power injector.

The nano has a limited beamwidth of around 53-55 degrees in the horizontal plane (depending on polarity) and 25 degrees in the vertical plane (depending on polarity)  and about a 15dbi FB ratio  meaning if your not on the right aim or if the wind blows the node made fall off off the list if not securely mounted.

It could also be polarity if you are running different than the rest of the group.

The big issue is the Gus's Nano Station is seeing my nodes on OHC (old Hillcrest) but the bullets and airgrids up there are not seeing Gus.  The only mesh node I can see getting through to Gus is HHE (new Hillcrest - East).  

The node is tying to send to a neighbor that doesn't see him directly.

We need to update the New Hillcrest to UBNT nodes and give Gus a better signal to latch onto.

Clint

Hello Clint,

Thanks that actually provides a bit of info as to why we are seeing what we are seeing.

So the LQ as displayed on that screen only looks at LQ which is the measure of how good YOUR NODE hears the REMOTE NODE.  

If you look on the OLSR status screen you will probably see a HIGH etx or even an infinite etx on DIRECT for the AE5CA node that cant hear you because the NLQ (You to the remote node)  is high and a good REMOTE path for it.

So in this case: your likely getting your HNA details through KF5NEP which may be getting low  on signal, especially its the node with the 0% LQ that you are seeing on the display (get the IP of the kF5NEP node to be sure)

Without at least one good bi-drectional link I cant guarantee that you to get all the packets you need to get name resolution in place (MPR selection can be at play here, only MPR nodes send TC/HNA/MID packets out to keep the duplicate flooding to a minimum  and I believe this will also include NAME SERVICE packets which are 100% needed  for name resolution)

So because of this you see IP addresses only until you can get a good link, once you have at least 1 good link the link changes to resolve names.

Keep an eye on the KF5NEP node's ip and see  if when once it shows up with a reasonable LQ and reasonable ETX that you actually start seeing names show up.