Nodes cannot accept incoming connections

AllStarLink
1

Hello. I own two nodes in different geographic locations, 52477 and 52478. Neither node will accept incoming connections, and in both cases, the port forwarding for UDP port 4569 has been verified to be set correctly. Is there something else that needs to be done to permit someone else to connect to my node?

Thank you,
Curt, N6ATC

2

Can you connect out?

3

Hi, Ken. Thanks for the reply.

Oh yes, outbound connections have worked for years with no problem.

4

I’m fighting a similar problem with a buddy’s node.

Have you verified the ports are open correctly by using, let’s say, netcat?

5

I’ve not, I’ve never used netcat. I’m looking into that now.

6

hmmm… I got this:

netcat -z -n -v 192.168.99.209 4569

192.168.99.209 4569 (iax): Connection refused

This is odd, because I know how to forward ports in my router (Ubiquiti UniFi UDM Pro) and I’ve checked it over and over and it is configured like every other open port that is working correctly.

7

On your ASL node, you need to stop asterisk (service asterisk stop). Then run

nc -l -u -p 4569

Then from another computer run:

echo "This is a test" | nc -u 192.169.99.209 4569

(assuming that IP is the IP of your ASL node). You should see “This is a test” appear on your node’s bash line. CTRL-c will stop the nc process on your ASL node, then you can restart (service asterisk start)

8

I don’t understand the second half of that instruction.

I understand stopping asterisk. That’s no problem.

Then from another computer run:

echo “This is a test” | nc -u 192.169.99.209 4569

Does that mean another computer that I SSH into the node with? I usually SSH in with PuTTY or MobaXTerm from my primary desktop computer in the shack. I would have to install that on a laptop or something to try it. Is that what I should do?

9

It looks like there is a problem connecting through that port. So I’m looking into it.

image

10

Please drop/disconnect local connections to your private nodes an try again.

Or test by connection to 49999

11

Checking a little deeper shows 52477 not actively registered. Perhaps it is off right now?.
Must be registered to be connectable.

12

Mike:

Thank you for the reply.

image.png

13

I should mention that my system is a HAMVoIP system, as I know that makes a difference. I will attempt to seek more assistance from those guys and document the resolution here if it occurs.

14

Not sure how this works in HAMVOIP but give this a try.
systemctl restart updatenodelist