I am assisting the WC5GC group in setting up a new Allstar node linked to their repeater. After moving the node to their EOC, the node fails to register with the Allstar directory. The node previously worked on another network. We have confirmed the 4569 port is forwarded correctly. I am able to connect to the node using a private node entry. but the node is not registering or updating the public Allstar directory. This “troubleshoot” page says to ask here about this problem on some NAT connections.
I see your node as registered as of a few hours ago, but not registered now. Can you provide some console logs to help us figure this out?
With verbose set to 10, all I see are messages about sending registration as shown below. I have also added the extra register record for “@register-central.allstarlink.org” suggested in another message here. But it didn’t seem to help. This node is running a Raspberry PI using a hamvoip image.
<asterisk console with verbose set to 10>
Asterisk 1.4.23-pre.hamvoip-V1.6.2-10 app_rpt-0.327-06/01/2020, Copyright (C) 1999 - 2020 HamVoIP.org and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.
Connected to Asterisk 1.4.23-pre.hamvoip-V1.6.2-10 app_rpt-0.327-06/01/2020 currently running on node53991 (pid = 12875)
[Apr 29 07:55:00] WARNING[12891]: chan_iax2.c:10270 iax2_do_register: REGISTER-LOG: Sending registration request for ‘53991’
[Apr 29 07:55:00] WARNING[12886]: chan_iax2.c:10270 iax2_do_register: REGISTER-LOG: Sending registration request for ‘53991’
[Apr 29 07:55:00] NOTICE[12886]: dnsmgr.c:209 dnsmgr_refresh: host ‘register.allstarlink.org’ changed from 162.248.92.131 to 34.105.111.212
reboot your network router and modem.
I wish that were the solution. It is not.
This node worked as expected when located at the home of one of the group officers. This issue started when it was relocated at the EOC.
I suspect this is an issue with the EOC network. The EOC network is tightly controlled and firewalled. However, other applications work fine, such as web browsing. And, they have forwarded network ports required for incoming Allstar connections.
I can connect to this node from my nodes after creating a “private” node number pointing to this nodes IP address. I tried creating private node numbers on the node pointing back to my nodes. That does not work.
I have also tried using a VPN. However, the node will not connect to the VPN server.
This leaves me to suspect the EOC network is filtering or modifying some outgoing network packets.
IAX registration is an outbound process, no port forwarding necessary for it to work. However it is conceivable the EOC network is only allowing certain outbound traffic.
Can you tell if there is any connectivity at all available to your node? I’m thinking maybe the gateway, mask or DNS is not correct.
There is connectivity from the node, at least to web sites and ping responses. I can also connect to the node using a private node definition from one of my Allstar nodes. I have not been able to connect from the node to my node using a private node definition. But I only tried that once. As I indicated before, I suspect the EOC network/firewall may be blocking some protocols or connections. But we have no way to purse analyzing and resolving that kind of the problem on the at the moment. If the Allstar directory servers are never seeing the attempts to update from the node, we’ll see if the EOC network support want to investigate further.
[root@node53991 tmp]# ping allstarlink.org
PING allstarlink.org (34.105.111.212) 56(84) bytes of data.
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=1 ttl=60 time=68.5 ms
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=2 ttl=60 time=68.5 ms
64 bytes from register-west1-b.allstarlink.org (34.105.111.212): icmp_seq=3 ttl=60 time=68.3 ms
[root@node53991 tmp]# curl https://whatsmyip.com/ -s | grep -oE “>([0-9]{1,3}.){3}[0-9]{1,3}<” -m1
24.117.89.66<
[root@node53991 tmp]# traceroute -I -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.9.120.161 0.708 ms 0.596 ms 0.574 ms
2 192.9.200.250 0.553 ms 0.743 ms 0.717 ms
3 24.117.89.65 11.665 ms 11.740 ms 11.665 ms
4 10.224.91.1 4.124 ms 5.335 ms 4.144 ms
5 74.125.147.132 4.597 ms 3.455 ms 3.522 ms
6 108.170.240.129 4.853 ms 4.420 ms 4.381 ms
7 72.14.234.61 8.541 ms 4.246 ms 4.889 ms
8 8.8.8.8 3.375 ms 2.617 ms 2.721 ms
[root@node53991 tmp]# traceroute -m 35 -I -w 1 -n 162.248.92.131
traceroute to 162.248.92.131 (162.248.92.131), 35 hops max, 60 byte packets
1 192.9.120.161 0.389 ms 0.638 ms 0.612 ms
2 192.9.200.250 0.591 ms 0.590 ms 0.642 ms
3 24.117.89.65 6.696 ms 6.788 ms 6.762 ms
4 10.224.91.1 7.132 ms 7.230 ms 7.207 ms
5 * * *
6 4.68.74.166 4.765 ms 4.483 ms 4.477 ms
7 213.155.130.179 14.154 ms 14.182 ms 14.107 ms
8 213.155.130.176 26.650 ms 25.540 ms 25.962 ms
9 64.74.97.253 25.321 ms 25.335 ms 25.276 ms
10 162.248.92.131 26.638 ms 26.444 ms 26.589 ms
[root@node53991 tmp]# traceroute -m 35 -I -w 1 -n 34.105.111.212
traceroute to 34.105.111.212 (34.105.111.212), 35 hops max, 60 byte packets
1 192.9.120.161 0.560 ms 0.784 ms 0.744 ms
2 192.9.200.250 0.720 ms 0.695 ms 0.671 ms
3 24.117.89.65 5.838 ms 5.802 ms 5.781 ms
4 10.224.91.1 6.417 ms 4.945 ms 4.912 ms
5 142.250.168.16 4.185 ms 4.392 ms 4.367 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 10.141.158.166 10.335 ms 10.446 ms 10.433 ms
16 172.253.76.122 12.386 ms 12.369 ms 10.171 ms
17 172.253.51.144 11.198 ms 11.255 ms 10.834 ms
18 209.85.250.46 10.717 ms 10.797 ms 10.729 ms
19 72.14.237.135 45.201 ms 45.027 ms 45.117 ms
20 108.170.235.197 69.811 ms 69.423 ms 69.861 ms
21 74.125.252.58 68.520 ms 68.453 ms 70.348 ms
22 216.239.42.51 70.582 ms 70.778 ms 70.686 ms
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 34.105.111.212 69.086 ms 69.394 ms 69.375 ms
I suppose this could be the NAT source port issue described at https://wiki.allstarlink.org/wiki/Troubleshooting#Allstar_Link_registration_fails_when_behind_a_NAT_router However, I doubt they are using anything like D-Link.
Netstat shows repeating attempts to connect to one of the directory servers on port 80. When I use curl to access that address it just returns the 301 moved permanently http header.
[root@node53991 ~]# netstat -tunp|egrep “(34.105.111.212|162.248.92.131)”
tcp 0 0 192.9.236.59:51214 34.105.111.212:80 TIME_WAIT -
tcp 0 0 192.9.236.59:51212 34.105.111.212:80 TIME_WAIT -
tcp 0 0 192.9.236.59:51210 34.105.111.212:80 TIME_WAIT -
tcp 0 0 192.9.236.59:51216 34.105.111.212:80 TIME_WAIT -
Looks like the IAX packets aren’t making it out of the EOC network. I grep’d the log for 24.117.89.66. Nothing there.
I would check and see if the EOC has a firewall of it’s own.
none ?
Perhaps even try a different port like 8120 (set-up in ASL node settings same as well)
It can take 10-15 minutes for connect information to propagate so you have to be patient.
Perhaps mention the ISP in your next message.