mirror of
https://github.com/pyMC-dev/pyMC_Repeater.git
synced 2026-10-30 19:51:59 +01:00
Region handling is broken #36
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/pyMC_Repeater#36
Reference in new issue
Block a user
So, I originally wrote this up differently.
I've since found out that "*" isn't supposed to repeat everything, it's just intended to repeat "unscoped" traffic.
Right now it's doing everything.
The feature request is to remove the "Global Flood Policy" button.
Allow "*" (unscoped) flood traffic as a rule.
Bonus points for being able to filter repeating by packet type (ADVERT, GRP_TXT, etc) and scope.
Perhaps the should ne an option like "ignore scopes" to behave like im pre-region firmware
That's kinda how it's behaving at the moment when "enable global flood" is enabled.
The problem is, when you enable regions pyMC blocks unscoped traffic, with no option to enable it.
That's not how regions are supposed to work.
So right now it either repeats everything, or just the regions you specify. There's no option to specify unscoped plus specific scopes, which is how regions are supposed to work.
The former behaviour is like a pre-region repeater, but the latter not consistent with the way regions are supposed to work.
They're supposed to behave kinda like vlan tags. Where "*" actually represents unscoped (or untagged in vlan terms) and then you have a whitelist of scopes that the repeater will forward, and if those scopes are allowed to flood or not. Unscoped is itself a scope, and should just be treated like a regular region scope, not a wildcard. It's quite poorly named by the MeshCore developers.
This has now been fixed.