Cloud Connection Issues

AllStarLink
1

Has anyone else have or solved node connection issues to a Allstar Cloud Hub? Best I can tell its an DNS issue. Example, node is connected to Cloud Hub from home internet. Node then is taken mobile and can not connect to Cloud Hub, but can connect to other non cloud Allstar nodes. Cloud Hub gets booted and issue is cleared. I also seen just booting a node can cause it not to be able to connect back to the Cloud Hub too.

Thanks David KG5RDF

2

What is “AllStar Cloud Hub”, is there a node number?

3

47996 - Its a Virmack server node.

4

Not sure what a cloud hub is. Can you elaborate?

6

I can connect to 47996. Which of your nodes is not able to connect to 47996?

7

I just verified that my 50980 node can connect to your node. Please try to connect to mine and let me know how it works.

8

Its a Virmack server node.

Would that be https://virmach.com?

9

Transition ip nodes, fixed to mobile. Right now I have node 50141 that can not connect to hub, but it connects to 48005. If I boot hub, they will be able to connect. I did find the white/black list makes it worse, so I removed it. On Allstarlink.org if you say yes to remote base it occurs more often on that node.

David KG5RDF
NCTC.INFO

10

Yes, that is correct.

David KG5RDF

11

Yes connected fine.

David KG5RDF

12

I have several. I rented Ubuntu Server 16.04 LTS. I loaded the following:

Then simply ran Allstar configuration and setup node. This way it does not relying on my home internet. Its for a 24 site linked repeater system that NWS uses.

David KG5RDF

13

David,
I am trying to sort through your issue, but I can’t really tell where you are having a issue or your setup.

So you have a server mounted in the cloud right ?

What nodes are having connection issues, the server in the cloud or ? inbound or outbound to what target ?

14

Guess I must not be using the app correctly. I have responded to all questions. Either my explanations are not clear or your not seeing them. Here is what I have previously posted.

Thanks David

" Transition ip nodes, fixed to mobile. Right now I have node 50141 that can not connect to hub, but it connects to 48005. If I boot hub, they will be able to connect. I did find the white/black list makes it worse, so I removed it. On Allstarlink.org if you say yes to remote base it occurs more often on that node.

David KG5RDF
NCTC.INFO "

Yes, I have the cloud hub 47996 Ubuntu Server 16.04 LTS. Issue is inbound and outbound. Some of the nodes that have had issues in the past. 516222, 475481, 475480, 43266, 52798. If I boot the hub it clears the issue and has for the above nodes. Current node having issues is 50141 last time I check. It can connect to other nodes. The best way to recreate the issue to connect a node on your home internet and connect it to the cloud hub. Now take this node mobile and run it off your phone in a car mobile. It will now not be able to connect to the hub, till the hub is booted. Its the change in dns/ip that seams to be linked to the issue. Never have had this issue on a non cloud hub.

15

You don’t want remote base for your application.

16

Sorry was refering to inbound nodes not hub.

17

I can only generically say that I have had issues with cell/mobile DNS but I can’t say that is your issue.
I just bought service with other carrier to fix my issue. Many 3rd tier providers have more issues because they have lower priority on cell tower channels.

When you are cell mobile, your ip address can change rapidly, most especially if you are near the boarder of cellular districts. So if that is a problem, a service like a rapidly updating dynamic dns may help.

Because ‘if’ your target server does not have a copy of your node# & correct ip , it will not allow connect.

You will need to look at your logs to have a window to what might be happening. To many possibilities from your description.

18

Any time a node reboots it will disconnect unless you do one of two things.

  • Do a permanent connection. Permanent connections survive if the far end reboots or a network outage recovers.
  • Create a startup macro. Startup macros run when a node starts.

Also note that it can take a while (maybe 10 minutes or more) for a new IP to propagate through the network.

There are two ways IP address resolution happens.

  • DNS. Available production HamVoIP, Beta ASL at this time.
  • A nodes file which is updated every 15 minutes.

Example DNS lookup:

nslookup 516222.nodes.allstarlink.org
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	516222.nodes.allstarlink.org
Address: 149.28.251.116

Example nodes file /var/lib/asterisk/rpt_extnodes:

grep 516222 /var/lib/asterisk/rpt_extnodes
516222=radio@149.28.251.116:4571/516222,149.28.251.116

If your could hubs are running ASL and your non cloud nodes are running HamVoIP, that could explain the different behavior.

The new ASL registration server supports DNS. The ASL Beta client supports only *cli>rpt lookup <node#> at this time.

19

That’s very nice. Never gave it a thought the mobile’s were hamvoip.

But one question… is there a change in registration string in iax.conf ? (for the new dns)

20

No. The client registration string does not change. DNS is populated by the ASL registration server. You can lookup any ASL node with <node#>.nodes.allstarlink.org.

21

Mike in my case I run both registrations so that’s a rabbit hole. It is not just mobiles, it was an example. I find non Hamvoip nodes have this issue more often and repetitive.