<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
From <a class="moz-txt-link-freetext" href="http://ohnosec.org/drupal/node/56">http://ohnosec.org/drupal/node/56</a><br>
<br>
<h3><i>Denying incoming connections from selected Echolink nodes</i></h3>
<i><br>
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:</i>
<ul>
<li><i>To deny w6xxx you would add the statement: deny=w6xxx
</i></li>
<li><i>To prohibit computer-based connections you would write:
permit=*-*
</i></li>
<li><i>To allow access to only a select group of callsigns:
permit=w6abc,w6def,...
</i></li>
</ul>
<br>
<br>
On 3/19/2011 15:32, Tony KT9AC wrote:
<blockquote cite="mid:4D852F18.1090908@ameritech.net" type="cite">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.
<br>
<br>
Thanks,
<br>
Tony
<br>
_______________________________________________
<br>
App_rpt-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
<br>
</blockquote>
</body>
</html>