[arm-allstar] live keyed nodes

[Patrick Perdue]

I have implemented a temporary solution to this problem, pending other 
developments.

Here's what I ended up doing.

The Raspberry Pi 3 model b plus hosts three private nodes. One is 
connected to the Arcom repeater controller, another is connected to the 
Yaesu HRI200, and the third is using the USRP channel driver.

The Raspberry Pi 4, which handles all the incoming IAX connections from 
the world, is also connected to USRP.

The three private nodes on the Pi 3 are connected together, but there is 
no IAX connection from the public node to any of the private ones. 
Instead, I have just pointed the USRP drivers at each other's ports and 
IP addresses. This allows traffic sent on either of the three private 
nodes to appear as if it's coming from the public node, as if a physical 
radio were attached, which is the behavior I'm going for.

This isn't without it's drawbacks, and will probably not be a permanent 
solution, but it works for now.

On both nodes, in modules.conf:

change the line

noload=chan_usrp.so

to

load=chan_usrp.so

Then, in rpt.conf, assuming node1's IP address is 192.168.1.20, and 
node2's IP is 192.168.1.21, node1's rxchannel looks like this:

rxchannel = USRP/192.168.1.21:39001:37001

and on node 2:
rxchannel = USRP/192.168.1.20:37001:39001
The ports are arbitrary. The important thing is not to use a set of UDP 
ports that are already in use, and to invert the IP addresses, RX and TX 
ports on the two nodes.
Make sure there is no telemetry, IDs, courtesy tones, etc. on both USRP 
nodes, unless you want that for a special use-case or something.

On 7/9/2022 9:30 AM, Patrick Perdue wrote:
> Hi:
>
> This is probably a question that is best posted to one of the 
> Allstarlink groups, but figured I'd ask here first.
>
> I have been helping the Sierra Foothills Amateur Radio Club (SFARC) 
> with their HamVoIP/WIRES x/other stuff.
>
> We recently went from a single Raspberry Pi 3 model B Plus connected 
> to an Arcom repeater controller, as well as a Yaesu HRI-200. It wasn't 
> up to the task of holding more than about 62 IAX connections without 
> falling over. So now, a Raspberry Pi 4 is in the vault, which is 
> acting purely as a radioless hub, with the old Pi dedicated to 
> maintaining two private nodes -- one connected to the controller, the 
> other on the HRI200.
>
> This is all working very well, and is much more stable than the 
> previous system.
>
> However, since the repeater is now on a private node, and those don't 
> report to Allstarlink's stats server, traffic sent via RF to the 
> repeater no longer shows on the live keyed nodes list. This group has 
> a well-known net every day at 7:30 AM Pacific, and people have been 
> known to check in from discovering it via live keyed nodes.
>
> So, my question is, other than creating yet another public node that 
> doesn't accept incoming connections, and has a note like "don't 
> connect here, use this other node" in, say, the frequency or PL field 
> on the associated server, is there any way around this? I've seen this 
> kind of thing on some systems.
>
> I expect probably not, but thought I'd ask here anyway.
>
> 73
>
> N2DYI
>