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

Corrupt mesh status current neighbor node name on TP-Link CPE 710 on 3.23.12.0 #1009

Closed
alchemy33 opened this issue Dec 11, 2023 · 4 comments
Labels

Comments

@alchemy33
Copy link

alchemy33 commented Dec 11, 2023

Node name of TP-Link CPE 710 V1 appears incorrect on Mesh Status page of RF connected nodes. The expected node name would be "KE3KQ-5G-ROFO" in the Current Neighbors field. The displayed name is "dtdlink.KE3KQ-5G-ROFO /KE3KQ-5G-ROFO.local.mesh". This name is evident on nodes of Mikrotik SXT 2 & 5 GHz and GL-USB150 2 GHz

This was also like this in 10/18/23 nightly builds and also remains this way in current firmware version release 3.23.12.0

Expected behavior is the node name to be displayed on other nodes as "KE3KQ-5G-ROFO". If dtd then this be appended after the node name and not as a prefix. The "/" and repeat of the node local address seems related. I suspect that this naming structure is related to other observations but this is the most obvious. All this is RF, as I do not tunnel. Installation of the current release firmware was uneventful.

I am attaching 2 images. One is the basic node status screen of the TP-Link CPE710 v1. The second is the mesh status page from an RF connect Mikrotik SXT node displaying the incorrect node name.

Images in comment post following.

Thanks for looking into this!

@alchemy33 alchemy33 added the bug Something isn't working label Dec 11, 2023
@alchemy33
Copy link
Author

Image of basic TP-Link CPE 710 v1 node screen.

IMG_0942

Image of how node name is displayed on an RF connected node

IMG_0941

@aanon4
Copy link
Contributor

aanon4 commented Mar 27, 2024

#1128

@aanon4
Copy link
Contributor

aanon4 commented Mar 27, 2024

This fixes the problem you're seeing. However, it's an install level fix so probably wont help you unless you reinstall the node from scratch.

@alchemy33
Copy link
Author

Wonderful! I installed the CPE710 factory.bin and sysupgrade.bin nightly 3/27/24 files last night and can confirm the node name fix as noted in #1128. Thanks Tim!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants