korbinianbauer

[The NeighborInfo module tracks and broadcasts information about a node's direct neighbors.](https://meshtastic.org/de/docs/configuration/module/neighbor-info/) I think this fulfills the original request. You'll have to read the contents of the packet yourself though,...

> node B would realize that C cannot see Router or node A How?

> One possible implementation is for nodes to broadcast who their neighbors are similar to how telemetry is done now. That would either always be outdated and fail a lot,...

> However, being able to quickly “shut off” nodes is unique to `ROUTER` and is very useful in certain cases (I think [@b8b8](https://github.com/b8b8) agrees). It can eliminate rebroadcasts of `CLIENT`s...

> I propose the following. > Preset Name = ModFast That would break the scheme that suggests Range+Speed and it's also very close to MedFast. "Long Faster" and "Long Turbo"...

@mrpatrick1991 That seems like an issue that should be discussed entirely separate from this one here. @kboxlabs gives a 404 for me

My understanding is that `CLIENT_BASE` is supposed to act as a sort of "remote antenna" for nearby nodes that can't be placed in advantageous positions themselves. Those nearby nodes basically...

> Was this behaviour not already added by [#7992](https://github.com/meshtastic/firmware/pull/7992) ? If I understand #7992 correctly, with this `CLIENT_BASE` decides to not decrement hops if the **previous** node is an infrastructure...

Frist things first, muzi works recommends flashing the latest Beta firmware, which would be 2.6.11.60ec05e at the time of writing. Does that behave differently? --- Apparently the R1 NEO needs...

> The R1 Neo should pull DCDC_EN_HOLD at boot via main.cpp: Well, yes, but what mechanism keeps supply voltage alive after calling `NVIC_SystemReset()` resets `DCDC_EN_HOLD` **until** `setup()` is executed when...