Modify / add a new setting to flood.max.unscoped to control group.txt separately

[mesher-de]

We see a lot of unnecessary and unscoped and flooded req/resp/anon requests in our local mesh here. (up to 30+ hops sometimes)

Limiting them with flood.max.unscoped works quite well but unfortunately also limits channel-messages quite early.
In some cases (border of 2-3 countries) unscoped messages work better than scoped messages as some people are just not capable to properly setup regions on their repeaters.

To address this I would like to suggest a modification for the flood.max.unscoped setting:

• Exclude grp.txt messages from flood.max.unscoped and
• Add a new setting e.g. flood.max.unscoped.chanmsg to limit them separately from other types

This would allow for a finer control and also solve some edge-cases like the one mentioned above.

I've compiled a firmware for testing and this works quite well (got very positive feedback from a few testers on the local mesh)

What are your thoughts on this? Good addition or too complicated?

[SaschaKt]

That is a great idea. So I can give more hops for group messages and cut off unscoped flood requests and responses 🤗

[SaschaKt]

When not set, the unscoped setting is active? If set, then it separates the group txt? Is it possible to set unscoped default to 5 and group txt to 64?

[mesher-de]

When not set, the unscoped setting is active? If set, then it separates the group txt? Is it possible to set unscoped default to 5 and group txt to 64?

The Idea is to always separate grp.txt from the rest; This gives you 2 settings;: a new one for grp.txt and the already existing one for the rest
So yes, this would allow your unscoped 5 and group txt 64

You could of course also limit group.txt to 5 and leave the rest on 64 if you want to

[netprince17]

Check out my PR, the situation might be similar...

#2797