-
Notifications
You must be signed in to change notification settings - Fork 67
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
NB 2159 - Nodes that have DtD links are reporting some RF links as Blocked - dtd #648
Comments
Support data for a Rocket M5 and a hAP showing this issue. More available if desired. supportdata-K6CCC-ROCM5-1-GLENDALE-202301142008.gz |
On a small sample size, reboot (or several) appears to clear this. Unknown yet if the fix lasts... |
Bit of a stab in the dark if I'm honest as I can't see how this could happen with the current code ... but various people have reported the problem. I've modified to code to be more active when choosing the block and unblocking by default - we'll see if that improves things. |
Glad I was not the only one seeing this one... |
Has this been fixed in the latest nightlies? |
Yes, the nightly build code has fixed this issue for me on the SXTsq5ac. THX |
Yes, it has been fixed on the various nodes where I observed the problem. |
I control 14 nodes that have a collection of RF and three separate DtD connections. All 14 nodes were updated to NB 2159 today.
A few hours after the updates, I discovered a node showing on the Neighbor Status page a RF link wth a Status of blocked - dtd. Started checking other nodes, and every single node that has one or more DtD neighbors AND one or more RF links is reporting some of the RF links as blocked - dtd. Nodes that are RF only do not show this issue.
It appeared that I could NOT communicate over the affected RF links (if there was no other path).
The text was updated successfully, but these errors were encountered: