Getting private nodes to connect

App_rpt-users
1

I’m setting up some private nodes and doing some preliminary testing at my home QTH before everything is deployed. I have 2 separate Pi3s, each set up as a private node. I’ve tested each one using Echo Mode and that works fine but I can’t get them to talk to each other over my LAN. Both connected to my AREDN router and both were successfully assigned IP.

In rpt conf on #1, I have under the [nodes] stanza

1000 = radio@127.0.0.1/1000,NONE ; Local node
1001 = radio@10.150.180.36/1001,NONE ; Remote node

In #2, I have

1001 = radio@127.0.0.1/1001,NONE ; Local node
1000 = radio@10.150.180.35/1000,NONE ; Remote node

As they’re both on the private side of the same LAN, I didn’t think I needed to open Port 4569 but I did anyway (for the hack of it)

I’ve checked the logs on each node but they don’t indicate anything

How can troubleshoot this?

2

Troubleshoot by opening the *CLI on both servers with verbose level 3 asterisk -rvvv or asterisk -r then core set verbose 3. Then connect one node to the other and watch what happens. Post the result here if you like.

Also, did you remember to set node number in extensions.conf?

3

Yes. both nodes are set correctly in extensions.conf

Nothing seems to be happening on either end. Here’s from the 10.150.180.35 one:

root@stn300:~# asterisk -rvvv

AllStarLink Asterisk Version 1.01 2/13/2018 GIT Version adaec47
Copyright © 1999 - 2018 Digium, Inc. Jim Dixon, AllStarLink Inc. and others.
Created by Mark Spencer markster@digium.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘core show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘core show license’ for details.

Connected to Asterisk GIT Version adaec47 currently running on stn300 (pid = 536)
Verbosity is at least 3
stn300CLI> core set verbose 3
Verbosity is at least 3
stn300CLI>

4

By the way, you say to “connect one node to the other”. Does that not happen automatically on boot on a private node?

Maybe THAT’s what I’m missing…

5

Nope, not automatically on boot. You have to set that up with a startup macro.

But first test connectivity: on node 1000, from the *CLI do rpt fun 1000 *31001

6

Aha! They’re connected. I ran the command on both nodes

As these will be full time links, I can just add (under the [macro] stanza for each node

startup_macro=*3 [the other node number]

7

Ahhh. got it. The startup_macro command goes in the nodes stanza… it’s working

Yet again, thanks for the help

8

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