I have 4 nodes using the ClearNode Ventures ClearRPT boards in a small local repeater network in NC. These have been working well. Two of the sites came offline, one due to power outage, the other a network issue. Site 593162 power was fixed today, the clearRPT rebooted and I can see the node on my iPhone using the ClearNode app. However it does not register on AllStarLink and cannot be linked into our hub 597790. The second site 593161 has been offline for a few days. I remotely rebooted the ClearRPT without success. This afternoon I plugged in 2 spare ClearRPTs at home on my network, they both booted fine and I can see both of them in the iPhone app but as above these nodes are not registering and indicating offline. Looking for some guidance how to proceed. thanks.
Did you try reloading the extensions file from Allstarlink? I had this problem before and that cleared it up,
You can also contact the ClearNode Support and he will help as well
This is not a clearnode issue as two other rpi nodes that are not clear nodes are also affected. How do I reload the extensions file from from Allstarlink?
thanks for the reply
You referenced only ClearNodes above. ClearNodes have specific configurations and their own software packaging. You should work with the ClearNode support people on those.
For normal, ASL3 packages the relevant stock configs are stored in /usr/share/doc/asl3-asterisk-config/examples/configs/asl3.
However, you don't happen to be on T-Mobile do you? Recent changes with T-Mobile's network architecture is incompatible with AllStarLink.
I have the same issues with my clearnode the last couple of days. Have reached out to clearnode support and they told me it is not a clear node issue but an allstar registration. Allstar thinks I am registered from an AWS IP address instead of my actual ISP WAN address and I can not figure out how to get it to re-register.
ALmost all registration problems are password related or network related. You didn't provide a node number or any logging or diagnostic output. At minimum, what's the node number and what's rpt show registrations say?
This is Gerry with Node-Ventures and the ClearNode products. We are now tracking several customers running HamVoIP that are failing to register. We’ve checked node #s, passwords, IAX Ports, Proxy IPs on the Server record - nothing I can see that’s wrong. Not all HamVoIP installations - I have several that work just fine. It’s not isolated to T-Mobile, although it could be CGNAT, one customer is on a regional ISP in Alaska. All are configured in iax.conf - “nodenumber:nodepassword@register.allstarlink.org”. No changes there in a long time.
Nothing at all has changed in HamVoIP for over 4 years, as you probably know, and similarly there’s nothing new on the networking side in the ArchLinux image.
Can you folks suggest how to debug the interaction with register.allstarlink.org ?
This is Edfil DV1OTT/DZ4E from the Philippines my node 614154 is also not registering
Connected to Asterisk 1.4.23-pre.hamvoip-V1.7.1-04 app_rpt-0.327-01/22/2022 currently running on DX1BBCLink (pid = 330)
Verbosity is at least 4
DX1BBCLink*CLI> 52.44.147.201:4569 Y 614154 60 Timeout
and also my friends node #s are not registering as well nodes 569080, 677799, 64065, 634050, 60399. 603970 and 556041
hope theres a fix for this thank you so much
All of my nodes quit registering as well. Two of them stay running 24/7. 512493 and 512494 01/26 at 08:33 UTC and 01/26 at 08:37 UTC was the last time they were seen. Now I cannot not connect to anything besides the parrot nodes, and the traceroute fails to register.allstarlink.org Two are SHARI nodes and one is a radioless node 512491. Probably been a minute since 512491 was seen, but I didn’t look.
All nodes are running Hamvoip, I’m on Starlink, and have had no issue until they stop registering unexpectedly. I have tried everything I can think of, and have searched the forums as well.
Is this possibly an Allstarlink issue?
Thanks!
I have about a dozen Hamvoip nodes out in the field. About 1/3 of them haven’t been able to register with register.allstarlink.org for the last 1-2 days and connect to our ASL3 hub. Oddly the other 2/3’rds are okay for now.
The Hamvoip nodes should all be the same software versions and up to date, no changes to IAX passwords or configs, but they are connected via a variety of internet service providers.
Hopefully can work out why soon!
Regards,
Rob…
VK6LD
Those having problems with connection issues - I’m using Starlink and after the latest Starlink update two days ago, my node no longer connects. I have checked with other local users using Starlink and they have the same problem.
I have no idea as to how this will be resolved.
Cheers Daryl - VK3AWA
I am also on Starlink. Have been for about 9 months and no issue till just a few days ago.
In order to figure anything out, I need people to actually provide some useful debugging information. What nodes, what the output of iax2 show registry says on broken nodes, if they're all HamVOIP using IAX2, etc.
Just as another data point:
I have one HamVoIP server that is hosting three nodes, and they all register.
allstar503683*CLI>
iax2 show registry
Host dnsmgr Username Perceived Refresh State
52.44.147.201:4569 Y 503683 72.89.237.157:1078 180 Registered
52.20.63.146:4569 Y 508421 72.89.237.157:1078 180 Registered
52.21.169.197:4569 Y 508420 72.89.237.157:1078 180 Registered
I have two more HamVoIP servers on the same IP, which both also register.
radioless*CLI>
iax2 show registry
Host dnsmgr Username Perceived Refresh State
52.44.147.201:4569 Y 508423 72.89.237.157:4566 180 Registered
And yet another HamVoIP node in a different location connected through a Tailscale exit node, which also registers.
linkbox*CLI>
iax2 show registry
Host dnsmgr Username Perceived Refresh State
52.21.169.197:4569 Y 508425 45.56.100.84:4570 180 Registered
None of these are clear nodes.
As an aside, I will one of these days get around to upgrading them all to ASL3. Just haven’t yet. One of them is still running on an rPi2.
I wonder if any of the HamVoIP nodes that can’t register have # in the registration line. For example, in iax.conf:
register=508420#4569:blahblahblah@register.allstarlink.org
If so, remove the # reference from the registration line, such that it looks like:
register=508420:blahblahblah@register.allstarlink.org
This one got me a few months ago, so it's probably not that, but worth a look anyway.
So a lot of the node numbers referenced in this thread, I don't see in the logging anywhere of them even attempting to register. Others are reporting as registering just fine in the logging. In some cases, I don't see them retrying every ~3 minutes as I would expect.
My nodes just registered after running iax2 show registry. 512491, 512493, 512494 I’m still on Starlink using Hamvoip.
It was saying Unregistered. (Now working again)
Nodes that had previously been unregistered for the past 24-48 hours, started re-registering correctly to Allstarlink just after 0405hrs UTC, 17 Jan 2026.
Many thanks.
Rob…
VK6LD
I restarted all of the registration servers around that time. This morning, I came up with a theory that I cannot test but I will share. Specifically because of how HamVOIP modified something with the registrations, we've seem "packet storms" of IAX registration attempts whenever something on the node goes wonky. There's a incoming IAX rate-limiter meter on UDP/4569 defined as follows:
udp dport 4569 meter iax2_srcip { ip saddr limit rate 10/second burst 20 packets } accept
udp dport 4569 drop
This creates a "token bucket" where any source IP can only send up to 20 UDP packets within a 2 second window. A standard IAX2 registration "handshake" usually takes 6 or 7 (don't remember offhand now which it was). If the source IP bursts beyond that, the connection is blocked until it stops long enough to "refill" the "bucket".
My working theory is that the Verizon outage combined with something else somehow triggered an on-network condition where the nodes that weren't properly registering were getting caught up in the meter. If this happens again, I'll simply flush the meter and see what happens.