[arm-allstar] Setting node

[Doug Crompton]

Jim,

  You need to precisely explain what he wants and doesn't want.

Do you mean echolink drivebys coming out over the repeater? That would be
solved by adding allow/deny calls to the echolink.cong file.

If you mean only allowing certain Allstar users that is another story. You
could make the node private as far as status is concerned by commenting out
the statposts. This would not stop someone from actually connecting as they
could still randomly connect to that node. It is not likely that would
happen though.

If you want to only allow certain RF users to access the Allstar commands
you can change the function codes to whatever you want. This is not really
secure though as tones on RF are sent in the clear and if someone wants to
figure it out they could.

If you want to ban or allow only certain Allstar user connects even if they
know the node number that can be done and I have written code to do that
but it generally is not a good idea. I use it only to ban real problems
which rarely occur. If everyone decided who could and couldn't connect then
we would not have much a network and everyone would be complaining they
could not connect somewhere thinking it was a technical issue.



*73 Doug*

*WA3DSP*

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

On Sat, Feb 11, 2017 at 3:18 PM, "James R. Pilgram via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Aloha Doug,
> I helped Danny set up his first node and what he was looking for was a
> node attached to a repeater with limited local access or some type of code
> to let those with a code access it. Seems the repeater owner doesn't want
> the drive by traffic. He's migrating away from EchoLink.  I was not really
> sure how to accomplish this as I have only done open nodes welcoming
> echolink drivebys giving me a chance to proselytize the virtues of Allstar
> and sway them from the dark side.
>
> Jim NH6HI
>
>
>   Original Message
> From: arm-allstar at hamvoip.org
> Sent: February 11, 2017 10:04 AM
> To: arm-allstar at hamvoip.org
> Reply-to: arm-allstar at hamvoip.org
> Cc: wa3dsp at gmail.com
> Subject: Re: [arm-allstar] Setting node
>
> Danny,
>
>   Not sure exactly what you want to do. Having a private node and no radio
> connection are two different things. Explain a little more what you want to
> do?
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Sat, Feb 11, 2017 at 2:03 PM, "Danny Williams via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I need to set up node for selective excess.  What ever is easiest,
> > Private node, turn off access to  radio or what ever you might surest!
> > KB5QP   Danny
> >
> > Sent from my iPhone
> > _______________________________________________
> >
> > 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
> >
> >
> _______________________________________________
>
> 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
> _______________________________________________
>
> 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