[Feature Request]: Enforced hop limits on packet relay for repeaters and routers

[noon92]

Platform

NRF52

Description

As meshes grow larger, the issue of users manually increasing hop limits will become more acute. Users assume that a higher hop limit is by necessity better - and in a perfect world of unlimited network capacity they'd be right. In our world, however, such users can cause major congestion, reducing the usability of the network for all, especially in locales with duty cycle maximums.

Right now, if a node receives a packet with a remaining hop count of 7, it will subtract 1 from that count and relay the packet, even if its own hop limit is set to 3.

Routers and repeaters are infrastructure nodes, and are usually placed in high up positions with good antennas. If such a node relays a packet with a high hop count, it can cause major congestion throughout the mesh over a large area.

I propose a new setting, Enforced Hop Limit, for routers and repeaters. With this setting enabled, if a router receives a packet with a remaining hop count higher than the hop limit, the hop limit will be lowered to the router's hop limit. Alternately, it could be lowered to one below the router's hop limit to simulate if it had been sent with a "proper" hop limit.

This setting could be enabled by admins in particularly congested meshes, especially if hop limit abuse becomes an issue.