[arm-allstar] Externaal Controller

[Doug Crompton]

Wayne,

 Assuming that the 1.5 code is setup with IRLP it would do exactly what you
are saying. You would setup pseudo ports for Echolink and IRLP. Just by
connecting or disconnecting them from the main Allstar node it would turn
them "on or off"

You also have to consider that Allstar and linux using Ethernet is in
effect a switch. There is no reason to put all your eggs in one basket. You
could have separate boards for each mode and even each Allstar node. They
would be connected at will via a local Ethernet LAN. This could even be
done in a private way without public Ethernet. Pi Boards are cheap!
Certainly a whole lot cheaper than a controller. Add ports to your content.

I am not a fan of trying to make one board do all. It is really not a good
idea from a redundancy standpoint. If that one board goes down you have
lost everything.



*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Tue, Jan 3, 2017 at 7:29 AM, "R. Wayne via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Of course I know that Allstar is a capable controller in its own right.
> But since I am the only coder, and not overly familiar with Allstar config
> files yet either, some of our team wants to use a separate external
> controller & port for Allstar, IRLP, EchoLink, etc. That way a novice admin
> can easily turn off a port if there’s a problem or a local net, what have
> you.
>
> Is there a practical advantage to doing so?. What are the disadvantages?
>
> I use some rather popular analog repeaters that are linked via IRLP and
> the 2m is on port 0, 70cm on 1, IRLP on 2 and EchoLink on 3. We’re going to
> add Allstar (I’ve convinced them!) Each has its own DTMF commands; do they
> conflict?
> _______________________________________________
>
> 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 web page - http://hamvoip.org