Skip to content

Conversation

@duraseb
Copy link

@duraseb duraseb commented Nov 30, 2025

🙏 Thank you for sending in a pull request, here's some tips to get started!

❌ (Please delete all these tips and replace them with your text) ❌

  • Before starting on some new big chunk of code, it it is optional but highly recommended to open an issue first
    to say "Hey, I think this idea X should be implemented and I'm starting work on it. My general plan is Y, any feedback
    is appreciated." This will allow other devs to potentially save you time by not accidentially duplicating work etc...
  • Please do not check in files that don't have real changes
  • Please do not reformat lines that you didn't have to change the code on
  • We recommend using the Visual Studio Code editor along with the 'Trunk Check' extension (In beta for windows, WSL2 for the linux version),
    because it automatically follows our indentation rules and its auto reformatting will not cause spurious changes to lines.
  • If your PR fixes a bug, mention "fixes #bugnum" somewhere in your pull request description.
  • If your other co-developers have comments on your PR please tweak as needed.
  • Please also enable "Allow edits by maintainers".
  • Please do not submit untested code.
  • If you do not have the affected hardware to test your code changes adequately against regressions, please indicate this, so that contributors and commnunity members can help test your changes.
  • If your PR gets accepted you can request a "Contributor" role in the Meshtastic Discord

🤝 Attestations

  • I have tested that my proposed changes behave as described.
  • I have tested that my proposed changes do not cause any obvious regressions on the following devices:
    • Heltec (Lora32) V3
    • LilyGo T-Deck
    • LilyGo T-Beam
    • RAK WisBlock 4631
    • Seeed Studio T-1000E tracker card
    • Other (please specify below)

@CLAassistant
Copy link

CLAassistant commented Nov 30, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@duraseb duraseb force-pushed the signal_based_routing branch 3 times, most recently from 1ab7822 to 11f5c94 Compare December 8, 2025 08:11
@duraseb duraseb force-pushed the signal_based_routing branch from a78171e to 22bcbcb Compare December 22, 2025 20:25
@duraseb duraseb force-pushed the signal_based_routing branch 2 times, most recently from c455d51 to 1b5e345 Compare January 11, 2026 13:46
…cks and logging, ensuring accurate node capability status updates and enhancing clarity in network topology logs.
…placing 'Capable' and 'Legacy' with 'SRactive' and 'SRinactive' for improved clarity in node participation and routing decisions. Introduce direct connectivity checks between nodes to enhance routing accuracy.
…dling, optimizing unicast relay coordination by implementing direct connectivity checks. Enhance unicast routing logic to utilize SR coordination based on any available route, improving network efficiency and reducing unnecessary transmissions.
…ction with fallback strategies, improving relay coordination and robustness. Introduce dynamic contention window checks for unicast packets, allowing for better handling of relay exclusions and optimizing network efficiency.
…s allows for more granular control over edge updates during topology broadcasts, improving network efficiency and accuracy in edge management.
…pology updates. Implement versioning for topology snapshots to prevent stale data processing and improve network reliability.
…ingModule to prevent topology pollution and improve network efficiency.
…e accuracy and simplifies timestamp management across the network topology.
…legitimate reverse edges during placeholder resolution.
…s. Ensure only legitimate edges are considered for direct communication.
… and unicasts. Enhance edge aging mechanism with capability-based TTL for improved network efficiency and accuracy in edge management.
…e limitations. Refactor contention window processing to evaluate relay decisions more effectively, ensuring only valid candidates are considered for unicast relays.
…ck conditions for uncovered neighbors. This ensures packet propagation when expected relays are unavailable, improving network reliability.
… improving topology accuracy and network efficiency.
…e to prevent issues with dynamic memory management and threading.
@duraseb duraseb force-pushed the signal_based_routing branch from 54d869c to c46a1ba Compare January 12, 2026 16:02
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.

2 participants