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

Add the ROUTER_INFILL role & supporting fields #632

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

erayd
Copy link

@erayd erayd commented Dec 8, 2024

This PR adds the new ROUTER_INFILL role & supporting fields for the following firmware PR:

meshtastic/firmware#5528

Will always rebroadcast packets, but will do so after all other modes.
Intended for router nodes that are there to provide additional coverage
in areas not already covered by other routers, or to bridge around
problematic terrain, but should not be given priority over other routers
in order to avoid unnecessarily consuming hops.
@CLAassistant
Copy link

CLAassistant commented Dec 8, 2024

CLA assistant check
All committers have signed the CLA.

@GUVWAF
Copy link
Member

GUVWAF commented Dec 9, 2024

What do others think about this idea and the naming?

@thebentern
Copy link
Contributor

I'm not the biggest fan of the naming, as it requires an explanation to users. How do we express the behavior in its simplest terms?

@erayd
Copy link
Author

erayd commented Dec 9, 2024

How do we express the behavior in its simplest terms?

ROUTER_LATE perhaps? Infill is what I intend to use this for (i.e. serving smaller pockets of population that are shadowed from our major high sites by annoying terrain), so I named it accordingly, but 'late' is descriptive of the actual behaviour.

@thebentern
Copy link
Contributor

Sounds good to me

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

Successfully merging this pull request may close these issues.

4 participants