[arm-allstar] echolink drive-bys

[Doug Crompton]

Greg,

 The end of the echolink.conf file has permit and deny settings:

power=20
height=50
gain=6
dir=0
;deny=
;permit=

Denying incoming connections from selected Echolink nodes

Echolink connections may be denied on a per-callsign basis. This is done by
using the deny and permit key values in the above [el0] stanza. The default
is to allow all connections if the permit and deny keywords are not
present. If a permit is specified, then only the callsigns specified in the
permit statement will be allowed to connect. If deny is specified, then the
callsign(s) specified will be denied access and the connection will be
terminated. Commas are used to delimit multiple callsigns for permit and
deny keys. Wildcards are supported so that whole classes of connections can
be rejected. Examples:

    To deny w6xxx you would add the statement: deny=w6xxx
    To prohibit computer-based connections you would write: permit=*-*
    To allow access to only a select group of callsigns:
permit=w6abc,w6def,...



*73 Doug*

*WA3DSP*

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

On Thu, Oct 6, 2016 at 9:41 AM, Greg via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> Getting really tired of the drive-bys (connect>disconnects). What is the
> correct way to block and allow certain nodes on the Echolink side?
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20161006/75e472df/attachment.html>