Update 10/15/2022, night: Got it! I was using the wrong name, as advised by a person on social media: "using iaxclient as username, not iaxrpt?" Yeah, I was using iaxrpt. Once I switched, DVSwitch connected immediately with no errors and I heard the hub announce the node number and my call sign. Success :-)
Update 10/15/2022, evening: I've got my ClearNode connected to my new hub node # 57945 (the Vultr-hosted node is 57945). There is no traffic on it, of course. I'm not sure yet if I have Echolink set up properly in the configuration. I'll need to find a few AllStarLink friends to help me test 57945 as a hub. Progress!
Update 10/15/2022: I've deployed a minimal server instance on Vultr.com and installed AllStarLink from a Debian 10 (beta) ISO. That went seamlessly. Where I've run into some trouble are a few details:
[1] I could not delete the ISO after installing the OS. The Vultr.com said it could not delete it because it was still attached to the IP address of the server. A quick request to support and 15 minute the deed was done.
[2] The DNS config in the Vultr dashboard was cryptic, to say the least. I went ahead and purchased a domain name but I'm not sure I'll need it. Nevertheless, that small piece is done.
[3] No firewall! I installed UFW and configured it to allow all outgoing connections and deny all incoming connections except those on port 4569. Once I figure out how to add Echolink to the ASL system, I'll need to open EL-specific ports to the UFW tables.
[4] I'm waiting for a second node number assignment from AllStarLink. My intention is to use the Vultr instance as a hub, and as a hub, no radio is actually required at the server. I'm sure I got the request out of sequence so I'm hoping that the ASL folks will recognize my intent and fix it when they assign a node number. Once the new node number is assigned, I can continue with configuring ASL on the cloud server.
Update 10/15/2022, night: Got it! I was using the wrong name, as advised by a person on social media: "using iaxclient as username, not iaxrpt?" Yeah, I was using iaxrpt. Once I switched, DVSwitch connected immediately with no errors and I heard the hub announce the node number and my call sign. Success :-)
Update 10/15/2022, evening: I've got my ClearNode connected to my new hub node # 57945 (the Vultr-hosted node is 57945). There is no traffic on it, of course. I'm not sure yet if I have Echolink set up properly in the configuration. I'll need to find a few AllStarLink friends to help me test 57945 as a hub. Progress!
Update 10/15/2022: I've deployed a minimal server instance on Vultr.com and installed AllStarLink from a Debian 10 (beta) ISO. That went seamlessly. Where I've run into some trouble are a few details:
[1] I could not delete the ISO after installing the OS. The Vultr.com said it could not delete it because it was still attached to the IP address of the server. A quick request to support and 15 minute the deed was done.
[2] The DNS config in the Vultr dashboard was cryptic, to say the least. I went ahead and purchased a domain name but I'm not sure I'll need it. Nevertheless, that small piece is done.
[3] No firewall! I installed UFW and configured it to allow all outgoing connections and deny all incoming connections except those on port 4569. Once I figure out how to add Echolink to the ASL system, I'll need to open EL-specific ports to the UFW tables.
[4] I'm waiting for a second node number assignment from AllStarLink. My intention is to use the Vultr instance as a hub, and as a hub, no radio is actually required at the server. I'm sure I got the request out of sequence so I'm hoping that the ASL folks will recognize my intent and fix it when they assign a node number. Once the new node number is assigned, I can continue with configuring ASL on the cloud server.