Describe the bug
When requesting NeighborInfo from a node (that has the necessary config enabled), the response packet is received, shown in the packet monitor and log, but then not shown in the UI. The last relevant log message is "[INFO] 📡 Processing 5 neighbors from !xxxxxxxx". The same behaviour is also observed at the periodic requests from meshmonitor to the local node.
To Reproduce
Steps to reproduce the behavior:
- Open the node message page for a node that meets the requirements (NeighborInfo enabled, FW 2.7.16+)
- Click on 'Request Neighbors'
- See packet monitor or logs, response appears
Expected behavior
In addition to the packet being logged, the neighbor information contained in the response should be processed, and then shown in the message page (similar to traceroutes), and on the map, if "show Neighbor Info" is enabled.
Environment (please complete the following information):
- Host OS: Linux
- Deployment type: Docker, v4.5.0
- Meshview is accessed through a reverse proxy
- Database backend: Default deployment (SQLite?)
- Node type: HeltecV4
- Node Connection Type: Wifi
Additional context
This issue has ocurred since v4.2.0 for sure, and possibly since v4.0.0. I only noticed it not working a bit after the big version jump, but it is possible to have happened earlier, and me not noticing. In v3.x.x this issue has not existed.
Let me know if more info/logs are required, I am happy to provide them if necessary :)
Describe the bug
When requesting NeighborInfo from a node (that has the necessary config enabled), the response packet is received, shown in the packet monitor and log, but then not shown in the UI. The last relevant log message is "[INFO] 📡 Processing 5 neighbors from !xxxxxxxx". The same behaviour is also observed at the periodic requests from meshmonitor to the local node.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In addition to the packet being logged, the neighbor information contained in the response should be processed, and then shown in the message page (similar to traceroutes), and on the map, if "show Neighbor Info" is enabled.
Environment (please complete the following information):
Additional context
This issue has ocurred since v4.2.0 for sure, and possibly since v4.0.0. I only noticed it not working a bit after the big version jump, but it is possible to have happened earlier, and me not noticing. In v3.x.x this issue has not existed.
Let me know if more info/logs are required, I am happy to provide them if necessary :)