Skip to content

feat: VLAN-style region tagging for untagged flood packets#2073

Open
dale-ruane wants to merge 1 commit intomeshcore-dev:devfrom
dale-ruane:dev
Open

feat: VLAN-style region tagging for untagged flood packets#2073
dale-ruane wants to merge 1 commit intomeshcore-dev:devfrom
dale-ruane:dev

Conversation

@dale-ruane
Copy link

@dale-ruane dale-ruane commented Mar 17, 2026

Summary

Closes #2041

  • Repeaters with a home region configured now automatically tag untagged flood packets (ROUTE_TYPE_FLOOD) with the home region's transport code, converting them to ROUTE_TYPE_TRANSPORT_FLOOD
  • Adds TRANSPORT_CODE_ALL (0xFFFF) as a reserved code that bypasses region filtering, allowing mesh-wide flooding when explicitly requested
  • Fully backwards compatible: repeaters with no home region set behave exactly as before

How it works

Similar to VLAN tagging in networking:

  • Untagged flood arrives + home region set → tagged with home region's transport code and forwarded
  • Untagged flood arrives + no home region → forwarded as-is (existing behaviour)
  • Tagged flood with ALL (0xFFFF) → always forwarded regardless of region config
  • Tagged flood with region code → existing region matching (unchanged)

Test plan

  • Repeater with no home region set forwards untagged floods as before
  • Repeater with home region set tags untagged floods with correct transport code
  • Already-tagged packets pass through unchanged
  • TRANSPORT_CODE_ALL packets are forwarded by all repeaters
  • Builds clean on ESP32 and NRF52 platforms

Repeaters with a home region configured now automatically tag untagged
flood packets (ROUTE_TYPE_FLOOD) with the home region's transport code,
converting them to ROUTE_TYPE_TRANSPORT_FLOOD. Also adds TRANSPORT_CODE_ALL
(0xFFFF) as a reserved code that bypasses region filtering, allowing
mesh-wide flooding when explicitly requested.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant