Connection failed to all nodes

I installed and configured my very first node. It is the only Pi on my home network. I followed all the steps in this youtube. https://www.youtube.com/watch?v=iCZsMFrVJlM&t=722s

Everything responded well, lots of pausing and entering to copy his setup. When I got to dialing nodes out I get connection failed. Some nodes ID themselves followed by connection failed. I have Frontier and the router does have port forwarding. I select UDP and 4569. But there is a global port range and local base port. I have tried all combinations to get it to work. Nothing comes of it. Maybe what I followed in the youtube video is not complete? I have port forwarding and trigger port options in my router. What am I missing?

What version of the software are you using ?
What is the node number in question ?

A port forward issue would only affect inbound network connections.
Node Registration would affect inbound and outbound.

Hi,
Node 62634.
Mobaxterm v24.2 build 5220
Ham VOIP rpi-z2w-2-3-4_v1.7-01_allstar

Hi there,

I am no expert but I use the Hamvoip image as well. I find that it takes a few minutes sometime to be able to connect to other nodes. How are you trying to connect, DTMF or Supermon/allmon?

I"m not sure why you’re asking in this forum about HamVOIP. Especially if you’re talking about the ASL3 installation videos. I would suggest starting with the documented process:

Dtmf. Tested that they are received correctly.

Just a noob feeling my way through something I know little about. Appreciate the info, I need to temper my excitement. Lol.

Can’t really say then. Like I said I use Hamvoip and it worked right out the box. I installed ASL3 and had problems with it and it turned out to be a bad SD Card and nothing to do with the software. I used and different card and work perfectly. Sometimes it is just something like that. But, like I said before, sometimes it takes a few minutes to be able to connect when you first start the node.

The registration process is not instant.
After you register at start, that info must be populated to all other registered nodes.
Some may update before others. It is discerned locally.
You must be in the list ‘they hold’ to be ‘valid’.

Until that happens, you have no connectivity inside the network.

On a reboot or offline for a short period of time, and your IP or port have not changed, you likely see no issue.
But when it is offline for extended period, you would be dropped from the list and have to wait for it to populate again.
Generally you are only looking at minutes, but some nodes may not be updating very timely.

Actually I solved the issue. Someone mentioned SD card issues. So I had a spare. I set up the same way I did before and it worked. When I try to read my original, it spins for a while and then nothing. Who would have thought a SanDisk would go bad like that. Thanks all for the feedback.

Good stuff. I was blown away too when it happened to me. Have fun.

Good the know. I power down my node every night so that explains it. Thanks so much.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.