Can't link to AWS hosted AllStar Hub
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
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 On Sun, 22 Apr 2018 19:13:04 -0400, BOB MEYER <bmeyer2929@cox.net> wrote:
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
-- Using Opera's mail client: http://www.opera.com/mail/
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@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
On Sun, 22 Apr 2018 19:13:04 -0400, BOB MEYER <bmeyer2929@cox.net> wrote:
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
-- Using Opera's mail client: http://www.opera.com/mail/
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/ cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
participants (3)
-
2E0SIP -
BOB MEYER -
Mike