# Getting private nodes to connect

**URL:** <https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387>\
**Category:** AllStarLink\
**Created:** [March 13, 2021, 4:03pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387 "2021-03-13T16:03:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![KenHorse](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/fbc32d/32.png) [@KenHorse](https://community.allstarlink.org/u/KenHorse)\
**Post date:** [March 13, 2021, 4:03pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/1 "2021-03-13T16:03:57Z")

</div>

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](mailto:radio@127.0.0.1)/1000,NONE ; Local node  
1001 = [radio@10.150.180.36](mailto:radio@10.150.180.36)/1001,NONE ; Remote node

In #2, I have

1001 = [radio@127.0.0.1](mailto:radio@127.0.0.1)/1001,NONE ; Local node  
1000 = [radio@10.150.180.35](mailto: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?

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [March 13, 2021, 4:17pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/2 "2021-03-13T16:17:31Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![KenHorse](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/fbc32d/32.png) [@KenHorse](https://community.allstarlink.org/u/KenHorse)\
**Post date:** [March 13, 2021, 4:28pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/3 "2021-03-13T16:28:19Z")

</div>

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](mailto: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  
stn300_CLI\> core set verbose 3  
Verbosity is at least 3  
stn300_CLI\>

---

<div class="post-metadata">

**Author:** ![KenHorse](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/fbc32d/32.png) [@KenHorse](https://community.allstarlink.org/u/KenHorse)\
**Post date:** [March 13, 2021, 4:33pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/4 "2021-03-13T16:33:39Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [March 13, 2021, 4:51pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/5 "2021-03-13T16:51:13Z")

</div>

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`

---

<div class="post-metadata">

**Author:** ![KenHorse](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/fbc32d/32.png) [@KenHorse](https://community.allstarlink.org/u/KenHorse)\
**Post date:** [March 13, 2021, 5:06pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/6 "2021-03-13T17:06:44Z")

</div>

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]

---

<div class="post-metadata">

**Author:** ![KenHorse](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/fbc32d/32.png) [@KenHorse](https://community.allstarlink.org/u/KenHorse)\
**Post date:** [March 13, 2021, 5:44pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/7 "2021-03-13T17:44:17Z")

</div>

Ahhh. got it. The startup\_macro command goes in the nodes stanza… it’s working

Yet again, thanks for the help

---

<div class="post-metadata">

**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\
**Post date:** [March 16, 2021, 5:44pm UTC](https://community.allstarlink.org/t/getting-private-nodes-to-connect/18387/8 "2021-03-16T17:44:41Z")

</div>

Closed on March 16, 2021, 5:44pm UTC

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