Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hAP lite reporting nodes as hidden when they aren't - NB 2283 and a few earlier. #711

Closed
k6ccc opened this issue Feb 12, 2023 · 2 comments
Closed

Comments

@k6ccc
Copy link

k6ccc commented Feb 12, 2023

At home, I have four nodes that are all able to communicate with each other on 2.4 GHz (channel -2). All four nodes are within six feet of each other, and can obviously see each other just fine. Until recently, all four nodes would report direct connections on the Mesh Status and Neighbor Status pages. The four nodes are:
K6CCC-hAP-at-Home (a hAP ac lite)
K6CCC-AR750-Portable
K6CCC-RB-LHG-2nD-XL (just the driven element - no reflector)
K6CCC-USB150-Portable

For the past few nightly builds, All of the nodes are reporting that they directly connect to each other except the hAP. The hAP will report one of the other nodes as a neighbor, but the other two as hidden. Which node is connected changes regularly. When this screen capture was taken, the hAP was connected to the USB150, but that changes regularly. I did a traceroute from the hAP and it also confirms that the hAP believes that the other two nodes are hidden.

Breaking news: Updated all four nodes to NB 2309 and after waiting for all four nodes to change Neighbor status from Pending, they are all reporting that they are directly connected. Traceroute on the hAP confirms direct connection. So this may be fixed in 2309...

hAP neighbors
hAP TraceRoute.txt
supportdata-K6CCC-hAP-at-Home-202302120934.gz
supportdata-K6CCC-AR750-Portable-202302120934.gz
supportdata-K6CCC-RB-LHG-2nD-XL-202302121735.gz
supportdata-K6CCC-USB150-Portable-202302120936.gz

@aanon4
Copy link
Contributor

aanon4 commented Feb 12, 2023

Going to hold off investigating this unless the issue returns.

@aanon4
Copy link
Contributor

aanon4 commented Feb 20, 2023

Closing as there's been no update on this with current firmware.

@aanon4 aanon4 closed this as completed Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants