-
Notifications
You must be signed in to change notification settings - Fork 543
Description
Hey There,
I'm looking at setting up regions and right now, it's super unclear on how they're supposed to behave.
Some section of the documentation suggest that setting the wildcard region, will allow ONLY traffic without region codes:
Then other sections of the docs seem completely contradictory, suggesting that a wildcard will allow BOTH with and without region codes, and then goes on to say traffic without region codes will be blocked.
It can't be both the latter two there, which is it? It can't both enable all regions for flooding, and apply onto to packets without transport codes. They are at odds with each other.
Because right now, after testing, I've found the firmware does not treat "*" as a wildcard, on 1.12 (I haven't been able to verify 1.13).
It would make sense for "*" to be wildcard, and repeat everything, and if you wanted to block traffic with region codes then setting an allow on something like "untagged" would make more sense to me.
Understanding how this behaviour is supposed to work is going to be critical to deploying larger meshes. It would make sense for "*" to be "repeat everything", "untagged" to only repeat traffic without a region code, and then the region-specific behaviour as it's documented.
It would be handy to further allow rules based on packet type (For example, allow */ADVERT/F) as right now applying a region to a repeater and denying flooding completely breaks Flood adverts.
Cheers,
Josh