[App_rpt-users] Can't link to AWS hosted AllStar Hub

[BOB MEYER]

Many thanks to those that responded. I didn't know about the tcpdump cmd, so thanks for the tip. I am indeed receiving udp 4569 traffic on the AWS-based node. I also added the 5060 udp port, and tried tcpdump 'udp 5060' but saw no traffic on that port. I don't think SIP is enabled by default on AllStar, and had seen no recommendations in the setup info, but thought it worth a try.

An additional bit of info: When the connection from a radio-based node fails, the CLI on it shows a message about "Auto-congesting call due to slow response". The same radio-based node can connect to other nodes, such as 2000, with no problem. I assume now, that the firewall/port configuration is not the issue, but something else. I see there are several wait timings in the rpt.conf file. I not sure if one of those is related to giving up too soon when the connection is attempted. 

Any other thoughts as to what might be going on? Has anyone been successful on another VPS?

Thanks in advance,
Bob KF5TVG

> Message: 2
> Date: Sun, 22 Apr 2018 18:13:04 -0500 (CDT)
> From: BOB MEYER <bmeyer2929 at cox.net>
> To: app rpt <app_rpt-users at lists.allstarlink.org>
> Subject: [App_rpt-users] Can't link to AWS hosted AllStar Hub
> Message-ID: <223235703.16158.1524438784236 at myemail.cox.net>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi all:
> 
> I'm new to the list, but have been working for awhile with AllStar nodes. I'm trying to set up a virtual PC hub on Amazon's AWS for several of us to link to, but get a "connection failed" audio announcement when I attempt to connect from one of our other nodes. I can log in to the hub, go to the CLI prompt and connect to other nodes from it just fine using "rpt fun <mynode> *3<other node>".
> 
> The udp port 4569 has been defined to accept connections from 0.0.0.0/0, ::/0 . It appears to be registered properly and the update node list is running. One of the FAQs indicates there may be a need to have the port set manually on the registration server. The node is question is 47527.
> 
> I'm running ASL version: GIT 004b9dd built by root @ stretch-64 on a x86_64 running Linux on 2018-03-01 18:39:13 UTC
> 
> If it is an issue with Amazon's AWS, and there is another VPS that does work, I'm not opposed to switching. 
> 
> I really like AllStar, and have put together some scripts and an Arduino to monitor heatsink temperatures and battery voltage on our radio-based nodes, and then announce the info on them when prompted. It is a fun and flexible system. Kudos to all involved in the design and ongoing development/support!
> 
> Many thanks in advance for any guidance,
> 
> Bob Meyer KF5TVG
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20180422/054a034c/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 3
> Date: Sun, 22 Apr 2018 20:06:52 -0400
> From: Mike <mike at midnighteng.com>
> To: "Users of Asterisk app_rpt" <app_rpt-users at lists.allstarlink.org>
> Subject: Re: [App_rpt-users] Can't link to AWS hosted AllStar Hub
> Message-ID: <op.zhwc9qkaf8cmrb at icool-w7d32>
> Content-Type: text/plain; charset="iso-8859-15"; Format="flowed";
> 	DelSp="yes"
> 
> Without really knowing what is going on...
> I would say to look at your firewall/ iptables and while you are at it,
> whitelist the ip's that will be using the system.
> Make sure 4569 can pass as well as 'udp' 5060
> 
> ...mike-kb8jnm
> 

> Message: 5
> Date: Mon, 23 Apr 2018 01:19:39 +0100
> From: 2E0SIP <app_rpt at marrold.co.uk>
> To: Users of Asterisk app_rpt <app_rpt-users at lists.allstarlink.org>
> Subject: Re: [App_rpt-users] Can't link to AWS hosted AllStar Hub
> Message-ID:
> 	<CAC-Lcd9aEnuDpQ7v+wZRzEG9r1LwqYSc16iY6fYNT3--dh54vg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Bob,
> 
> AWS has it's own firewall in front of your EC2 instance. To confirm its
> setup correctly, I'd suggest a packet capture.
> 
> Run the following in a terminal on your instance:
> 
> sudo tcpdump 'port 4569'
> 
> And then try to connect. See if you see any traffic going back and forth.
> 
> One other thing to keep in mind is a node will refuse connections if the
> connecting node hasn't been registered in some time. So if you try to
> connect with a new node, it will be rejected until the lists are updated.
> 
> Cheers
> 
> 
> On Mon, Apr 23, 2018 at 1:06 AM, Mike <mike at midnighteng.com> wrote:
> 
> > Without really knowing what is going on...
> > I would say to look at your firewall/ iptables and while you are at it,
> > whitelist the ip's that will be using the system.
> > Make sure 4569 can pass as well as 'udp' 5060
> >
> > ...mike-kb8jnm
> >