[arm-allstar] live keyed nodes

[Dave Petrie]

for a little effort why not try simply replacing the old raspberry pi with
the new one and keeping the same sd card and other equipment


On Sat, Jul 9, 2022 at 10:53 AM "Patrick Perdue via ARM-allstar" <
arm-allstar at hamvoip.org> 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
>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>