Put the static IP address for the central node in the remote rpt.conf’s they all call themselves 127.0.0.1. Have them all initiate connections to the central node. I think that should work. I don’t think the central node needs the remote IP addresses if it isn’t calling to them. I think. I have to try that some time. _____5 minutes later_____ OK, I tried this on my remote node. The “central node” has an incorrect IP address for the remote node. The remote node has the correct IP address for the central node in its rpt.conf file. I commanded the remote node to connect to the central node, worked fine. That scheme should work for you. Assume 1999 is central node and 1998 is remote. In central 1999 rpt.conf: 1998 = radio@192.168.xxx.yyy:4569/1998,NONE Then in remote 1998 rpt.conf: 1999 = radio@rea.lip.add.res:4569/1999,NONE “rpt reload” on each end and it should work. GeorgeC W2DB 2360 From: Mihhail Jakovlev Sent: Saturday, February 15, 2014 4:08 PM To: mailto:app_rpt-users@ohnosec.org Subject: [App_rpt-users] private nodes with dynamic IP Hi all, I am a new app_rpt user, I have a server with installed ACID, server have static IP. I have 3 assembled RTCM boards configured as voting repeater, it works fine. One RTCM can work as simplex node too. I was compiled app_rpt for Raspberry pi with SimpleUSB, it works, but I have question: How I can connect 2 maybe 3 or more) PC based „slave“ nodes (endnodes with radio connected) to „master“ server, if only „master“ server have a static IP, and all endnodes use dynamic? Two nodes in local network with static IP works fine All my nodes a private system(s), not in Allstar network. Master server have static IP, and all endnodes (PC based and RTCMs have dynamic addresses) Thanks! Mihhail Jakovlev ES1BIS