It is working with 58.65.173.10 which shall be removed by my ISP in one or two days as it is a temp IP given to me. with 58.65.173.10 it works without any change to ASL configuration files but with the other IP’s it does not. Seems IP addresses are blocked / get banned at some level as the difference of TX and RX packets between node and ASL reg servers. I have experienced country / region based ban on some forums and web services on internet before and it might be something like that.
Are you changing the gateway and name server with the new IPs? the filber connection is terminated with a GPON CPE in the datacenter from which one ethernet port is directly connected to the node on which these IP addresses are subnet'ed and have their individual gateways all using 8.8.8.8 and 8.8.4.4 as dns resolvers.
Can you ping register.allstarlink.org with the new IPs? yes I can ping and resolve all hosts behind register.allstarlink.org CNAME with all the 3 IP's as in above thread, I have mentioned that I can ping and provided sample traceroute output from all IPs.
That post was about the stats server. IAX registration is a separate server. Two separate systems. I doubt there is a block.
Have you tried another IAX port? Maybe switch to 4570, virtually any number will work. Remember to set the server settings on www.allstarlink.org to the same port.
Respectfully, I understand both are separate systems and the problem at that time was with stats, not to argue but my point humbly was that if my ISP’s entire ip segment block
was allowed at that time, means there was a white/black list at some level and the reg service may also have some kind now. I can understand implementation of security of systems and acknowledge there should be safeguards.
as for IAX port testing , I am running another node 48092 on another pi at my place currently with the public IP 39.32.9.40 (dynamically assigned not static as every reboot of CPE gets assigned new public IP by ISP at my place) which has never been used before to connect to allstarlink before today and IAX port is 4592 with the server settings @ allstarlink.org port is 4592, that to is not registering and shows the same symptoms.
ASLCLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
178.32.160.82:4569 Y 48092 <Unregistered> 60 Request Sent
ASLCLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
178.32.160.82:4569 Y 48092 <Unregistered> 60 Timeout
Interesting. It sounds like an ISP (in the middle) may be blocking some traffic from Pakistan. I’m not sure what the laws regarding communications their are or in the network path. Run a traceroute from each of those IP’s to register.allstarlink.org , www.allstarlink.org , stats.allstarlink.org and send those in an email to helpdesk@allstarlink.org. Then, one more test. Change the port used from 4569 to something else maybe 4965 for example. Don’t forget to change the setting in the “server” setup on the ASL portal.
It is also possible the ISP is splitting traffic and sending certain data types via different IP’s I have seen that more and more with cellular data carriers but possibly something that an ISP is doing
Are you changing the gateway and name server with the new IPs? the filber connection is terminated with a GPON CPE in the datacenter from which one ethernet port is directly connected to the node on which these IP addresses are subnet'ed and have their individual gateways all using 8.8.8.8 and 8.8.4.4 as dns resolvers.
Can you ping register.allstarlink.org with the new IPs? yes I can ping and resolve all hosts behind [register.allstarlink.org](http://register.allstarlink.org) CNAME with all the 3 IP's as in above thread, I have mentioned that I can ping and provided sample traceroute output from all IPs.
The iax2 show registry command sufficient to see registration status and easier to read. Please post that output for the bad IPs? Where is the new IP placed, directly on your node or a NAT router? Are you changing the gateway and name server with the new IPs? Can you ping register.allstarlink.or…
Many ASL people are working on your problem and trying to help out.
You created several helpdesk tickets and they were forwarded up the chain, there are a few quietly working behind the scenes on your “UNIQUE” issue.
It appears that there is some kind of CGN from your ISP going on and that may be causing problems.
I am sure you will be contacted directly to help you out. Once there is a solution we can post here for others to learn.
73
Marshall - ke6pcv
···
From: Shehzad via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org] Sent: Tuesday, May 26, 2020 10:11 AM To:ke6pcv@cal-net.org Subject: [AllStarLink Discussion Groups] [App_rpt-users] Node 50249 not being registered
Interesting. It sounds like an ISP (in the middle) may be blocking some traffic from Pakistan. I’m not sure what the laws regarding communications their are or in the network path. Run a traceroute from each of those IP’s to register.allstarlink.org , www.allstarlink.org , stats.allstarlink.org and send those in an email to helpdesk@allstarlink.org. Then, one more test. Change the port used from 4569 to something else maybe 4965 for example. Don’t forget to change the setting in the “server” setup on the ASL portal.
The node was originally running with public IP 203.99.60.213 which stopped working on 19th May till date. Today after discussion with ISP Core team, I got a test IP 58.65.173.10 and 210.2.163.185.
with 203.99.60.213 as public IP, no registration
with 210.2.163.185 as public IP of the node, the problem remains the same
with 58.65.173.10 and wollah , everything came back to life. these IP’s are all allocated to us form our ISP and no blocking is done from their end.
repeater*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
178.32.160.82:4569 Y 50249 58.65.173.10:4569 60 Registered
Connected to Asterisk GIT Version 004b9dd currently running on VMASL (pid = 350) Verbosity is at least 10 Core debug is at least 10 VMASLCLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 178.32.160.82:4569 Y 480920 …
I have been up in arms with the my ISP’s providing services in our datacenter, got one of the ISP to ensure no kind of CGN is deployed after a detailed session with their CTO to provide the required service, my node 48092 is online. I am still head to head with the other for 50249 node original IP .