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

Feature request: implicit neighbors for mqtt nodes #9

Open
prokrypt opened this issue Apr 2, 2024 · 2 comments
Open

Feature request: implicit neighbors for mqtt nodes #9

prokrypt opened this issue Apr 2, 2024 · 2 comments

Comments

@prokrypt
Copy link

prokrypt commented Apr 2, 2024

for nodes with fw 2.3+ which don't have neighborinfo enabled, implicit neighbors will be the ones with hop_limit==hop_start

@liamcottle
Copy link
Owner

If you could give some extra details on this, I could potentially add another layer to the map.

I probably wouldn't want to pollute the neighbours layer directly, since these aren't from the neighbour packets.

But, if you could give a few packet examples on how I can determine this, I'll have somewhere to start.

Saving these might get annoying, and how to expire them. Currently, when I receive a neighbour info packet, the database just completely overwrites the old neighbour info on the node entry.

However, if we are determining neighbours based on various different packets over time, I wouldn't be able to just overwrite that entry in the db, and we would probably have to track these implicit neighbours in their own database table.

@BillyBag2
Copy link
Contributor

I don't think this is anything to do with the neighbourinfo. I think this is a separate hop count feature. I think it will only work to "gateway" nodes. However you can deduce hop count from other nodes to the gateway by subtracting hop limit from hop count.
As far as GUI is concerned I think you would add a hop count to all nodes markers that you have the information for. It is only up to 7. I think zero is direct. Perhaps add a D.
May be add lines to direct nodes.
Maybe add a "hull" line that would be a guide to the range of a gateway node.

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

3 participants