Summary
Add the ability for pyMC_Repeater to filter/drop packets that meet certain criteria. This would allow an alternative to region scoping to prevent outside traffic that should be otherwise scoped. This logic should be similar to the existing token bucket system used to prevent overly-frequent ADVERT packets.
Why this matters now
-Medium to large meshes are starting to merge with one another. Some may have very good coordination with region scoping and flood control on traffic intended to stay localized while neighboring meshes are flooding locally focused traffic over other regional meshes that cover several states.
-With the advent of wardriving and bots, sometimes half a dozen replying to a single query, there has been an influx of non-human traffic (spam) that should really be constrained to a specific area unless really necessary to the wider mesh.
-The only option currently is to denyf * and stop all flooding and force all traffic to be region scoped to be repeated (not optimal).
What to add
Allow options under the repeater settings about whether to flood repeat based on the following criteria:
- Specific hashtag channel with a;
-- Location over a certain distance
-- Path Hop count over a certain number
-- Any traffic on this hashtag channel
- Packet originating from a bot by;
-- Token bucket system
-- Location over a certain distance
-- Path Hop count over a certain number
-- Any packet originating from a specific originating ID
Out of scope
- Region enforcement (exists, works)
- Path Hash Size issues (not relevant)
- Hardware (routing logic, not hardware)
Summary
Add the ability for pyMC_Repeater to filter/drop packets that meet certain criteria. This would allow an alternative to region scoping to prevent outside traffic that should be otherwise scoped. This logic should be similar to the existing token bucket system used to prevent overly-frequent ADVERT packets.
Why this matters now
-Medium to large meshes are starting to merge with one another. Some may have very good coordination with region scoping and flood control on traffic intended to stay localized while neighboring meshes are flooding locally focused traffic over other regional meshes that cover several states.
-With the advent of wardriving and bots, sometimes half a dozen replying to a single query, there has been an influx of non-human traffic (spam) that should really be constrained to a specific area unless really necessary to the wider mesh.
-The only option currently is to
denyf *and stop all flooding and force all traffic to be region scoped to be repeated (not optimal).What to add
Allow options under the repeater settings about whether to flood repeat based on the following criteria:
-- Location over a certain distance
-- Path Hop count over a certain number
-- Any traffic on this hashtag channel
-- Token bucket system
-- Location over a certain distance
-- Path Hop count over a certain number
-- Any packet originating from a specific originating ID
Out of scope