Does anyone have a simple way to create an access list for chan_echolink? I get a lot of quick connect/disconnects and want to block the random drifters. Thanks, Tony
On the same topic ... has anyone figured out how to play a connect message to Echolink? I am guessing that the reason they disappear is that they do not hear anything. The ID and tail-message do not come out on E/L Ken
-----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users- bounces@ohnosec.org] On Behalf Of Tony KT9AC Sent: Saturday, March 19, 2011 6:33 PM To: app_rpt mailing list Subject: [App_rpt-users] Access List for chan_echolink
Does anyone have a simple way to create an access list for chan_echolink? I get a lot of quick connect/disconnects and want to block the random drifters.
Thanks, Tony _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
From http://ohnosec.org/drupal/node/56 /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,... / On 3/19/2011 15:32, Tony KT9AC wrote:
Does anyone have a simple way to create an access list for chan_echolink? I get a lot of quick connect/disconnects and want to block the random drifters.
Thanks, Tony _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Perfect! Thank you Steve. Steve Passmore wrote:
From http://ohnosec.org/drupal/node/56
/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,... /
On 3/19/2011 15:32, Tony KT9AC wrote:
Does anyone have a simple way to create an access list for chan_echolink? I get a lot of quick connect/disconnects and want to block the random drifters.
Thanks, Tony _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (4)
-
Ken -
KT9AC -
Steve Passmore -
Tony KT9AC