Skip to content

Allow direct message paths when denyf * is set - alternative approach #2398

@ekjf0943vc

Description

@ekjf0943vc

PR1810 #1810 deals with enabling DM when denyf* ist set. I would like to suggest an idea that should render the same result, but without messing with the implementation of denyf* itsself.

I suggest adding two new rules:

  • allowg *
  • denyg *
    for GRP_TXT, GRP_DATA, ADVERT respectively.

I can't implement it, but hope someone here can do this easily.

I would like to thank dt267 dt267/MeshCore-Low-Power-Firmware-For-Heltec-V3-V4#6 for the suggestion.

This would not break the implementation of denyf* while enabling the above mentioned protocols. I hope this suggestion has better chances then PR1810. This would also end the endless support question concerning PR1810 and how denyf* works in main vs. evo respectively.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions