# Was the Echolink Random or Unknown Nodes Issue FIxed?

**URL:** <https://community.allstarlink.org/t/was-the-echolink-random-or-unknown-nodes-issue-fixed/22997>\
**Category:** Archive\
**Created:** [March 5, 2025, 8:53pm UTC](https://community.allstarlink.org/t/was-the-echolink-random-or-unknown-nodes-issue-fixed/22997 "2025-03-05T20:53:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![W4DTO](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/3e96dc/32.png) [@W4DTO](https://community.allstarlink.org/u/W4DTO)\
**Post date:** [March 5, 2025, 8:53pm UTC](https://community.allstarlink.org/t/was-the-echolink-random-or-unknown-nodes-issue-fixed/22997/1 "2025-03-05T20:53:20Z")

</div>

Not trying to rush anything, but I saw something recently that made me wonder if the Echolink issue in this subject line was resolved. I can’t find any info on it now but, I thought I saw something that said the issue was closed. If it was closed, can I beg someone to tell me how to patch my system so I can move forward?

Again, I understand priorities, and I’m not trying to push on this. Just hoping I can get it as quickly as possible once it’s resolved.

---

<div class="post-metadata">

**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\
**Post date:** [March 5, 2025, 9:16pm UTC](https://community.allstarlink.org/t/was-the-echolink-random-or-unknown-nodes-issue-fixed/22997/2 "2025-03-05T21:16:09Z")

</div>

If you are thinking about / referring to [GitHub app\_rpt Issue #434](https://github.com/AllStarLink/app_rpt/issues/434) then, yes, we have a fix. As to when it will be available I’ll share some insights.

- you, or someone else, creates a GitHub issue (done)
- you, or someone else, creates a GitHub pull request that corrects the issue (done)
- we merge the pull request into our main development branch (done)
  - Note: while this “closes” the issue it does not reflect whether it has been released in an update

- we create a new set of packages with all of the accumulated changes (in progress)
- we release the new packages to our “beta” testers (soon)
- we release the updated packages to everyone

In short, we have a fix for the noted issue and it’s on it’s way. We just need to get the packages put together, tested, and released.

---

<div class="post-metadata">

**Author:** ![W4DTO](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/3e96dc/32.png) [@W4DTO](https://community.allstarlink.org/u/W4DTO)\
**Post date:** [March 5, 2025, 10:27pm UTC](https://community.allstarlink.org/t/was-the-echolink-random-or-unknown-nodes-issue-fixed/22997/3 "2025-03-05T22:27:47Z")

</div>

THANK YOU for the fix and for taking the time to explain the process! I appreciate all of the effort that goes into the development and maintenance of excellent software.

Patiently waiting for that future release…