MeshCore v1.16.0 brought in some additional commands for scoped and advert max hops
openHop currently allows unscoped (*) as either on, or off - where as having a parity command (even if terminal only) or via UI would allow more consistent configuration to standard meshcore firmware.
New CLI config var ‘flood.max.unscoped’ #2661
New CLI config var ‘flood.max.advert’ #2702
Limiting Unscoped Traffic
The new flood.max.unscoped CLI config variable is specifically for limiting unscoped flood traffic. Like flood.max, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially off.
Limiting Advert Traffic
The new flood.max.advert CLI config variable is specifically for limiting adverts. Like flood.max, it drops advert packets which have already had a given number of hops. By default it is 8.
MeshCore v1.16.0 brought in some additional commands for scoped and advert max hops
openHop currently allows unscoped (*) as either on, or off - where as having a parity command (even if terminal only) or via UI would allow more consistent configuration to standard meshcore firmware.
New CLI config var ‘flood.max.unscoped’ [#2661](https://github.com/meshcore-dev/MeshCore/pull/2661)
New CLI config var ‘flood.max.advert’ [#2702](https://github.com/meshcore-dev/MeshCore/pull/2702)
> Limiting Unscoped Traffic
>
> The new flood.max.unscoped CLI config variable is specifically for limiting unscoped flood traffic. Like flood.max, it drops unscoped flood packets which have already had a given number of hops. By default it is 64, which is essentially off.
> Limiting Advert Traffic
>
> The new flood.max.advert CLI config variable is specifically for limiting adverts. Like flood.max, it drops advert packets which have already had a given number of hops. By default it is 8.
<!-- github-sync-id:5307449175 -->
For anyone who wants this now: SpamGuard 6.0 (an openHop plugin) adds both as settings, a hop limit for unscoped flood packets and one for adverts, with the same meaning as MeshCore's flood.max.unscoped and flood.max.advert. It writes them as openHop policy rules, much like the example above, and leaves your own rules alone. https://github.com/flackrat/openhop-spamguard
For anyone who wants this now: SpamGuard 6.0 (an openHop plugin) adds both as settings, a hop limit for unscoped flood packets and one for adverts, with the same meaning as MeshCore's `flood.max.unscoped` and `flood.max.advert`. It writes them as openHop policy rules, much like the example above, and leaves your own rules alone. https://github.com/flackrat/openhop-spamguard
<!-- github-comment-id:6231234773 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
MeshCore v1.16.0 brought in some additional commands for scoped and advert max hops
openHop currently allows unscoped (*) as either on, or off - where as having a parity command (even if terminal only) or via UI would allow more consistent configuration to standard meshcore firmware.
New CLI config var ‘flood.max.unscoped’ #2661
New CLI config var ‘flood.max.advert’ #2702
I thinks this can be emulated by policy rules:
For anyone who wants this now: SpamGuard 6.0 (an openHop plugin) adds both as settings, a hop limit for unscoped flood packets and one for adverts, with the same meaning as MeshCore's
flood.max.unscopedandflood.max.advert. It writes them as openHop policy rules, much like the example above, and leaves your own rules alone. https://github.com/flackrat/openhop-spamguard