Blacklist or whitelist - Revision history

KM4NNO at 16:00, 1 January 2021

2021-01-01T16:00:27Z

2020-01-27T18:32:35Z

Web Portal

2020-01-27T18:31:52Z

Web Portal

2020-01-27T18:31:25Z

2017-10-16T23:07:03Z

2017-10-16T23:05:40Z

2017-10-16T23:04:55Z

2017-10-16T23:03:52Z

2017-10-16T23:02:43Z

2017-10-16T23:01:33Z

@@ Line 57: / Line 57: @@
 == Web Portal ==
-If you want to have a blacklist for the web portal users you will need to modify the [allstar-public] context in extentions.conf
+If you want to have a blacklist for the web portal users you will need to modify the [pttlink-public] context in extentions.conf
 <pre>
-[allstar-public]
+[pttlink-public]
 exten => s,1,Ringing
-exten => s,n,Set(RESP=${CURL(https://register.allstarlink.org/cgi-bin/authwebphone.pl?${CALLERID(name)})})
+exten => s,n,Set(RESP=${CURL(https://register.pttlink.org/cgi-bin/authwebphone.pl?${CALLERID(name)})})
 exten => s,n,Set(NODENUM=${CALLERID(number)})
 exten => s,n,GotoIf($["${RESP:0:1}" = "?"]?hangit)

← Older revision		Revision as of 18:32, 27 January 2020
Line 89:		Line 89:

	To block a web-portal user you will need to add the callsign in capital letters to the blacklist.		To block a web-portal user you will need to add the callsign in capital letters to the blacklist.
−	** <code>*CLI> database put blacklist KM6RPT "no comment"</code>	+	* <code>*CLI> database put blacklist KM6RPT "no comment"</code>

@@ Line 84: / Line 84: @@
 exten => s,n(blacklisted),Wait(1)
 exten => s,n(blacklisted),Hangup
-<pre>
+</pre>
 Whitelist is not implemented here, but it should be easy to do

@@ Line 55: / Line 55: @@
 transfer = no
 </pre>
 [[Category:How to]]
 [[Category:Node Configuration]]

@@ Line 1: / Line 1: @@
-Occasionally it becomes necessary to limit connections to your node. With this configuration you can either blacklist (block) or whitelist (allow) inbound connections. Outbound connections are not blocked. The lists are managed with these Asterisk CLI commands:
+Occasionally it becomes necessary to limit connections to your node. With this configuration you can either blacklist (block) or whitelist (allow) inbound connections. Outbound connections are not blocked. Only one list can be used at a same time and it applies to all nodes on the server. If using the whitelist all nodes on the local server (127.0.0.1) are allowed. The lists are managed with these Asterisk CLI commands:
 * Blacklist
@@ Line 55: / Line 55: @@
 transfer = no
 </pre>
 [[Category:How to]]
 [[Category:Node Configuration]]

@@ Line 12: / Line 12: @@
 ** <code>*CLI> database show</code>
-''Note'': WA3DSP wrote a [https://hamvoip.org/downloads/node-ban-allow.sh menu script] for above commands.
+''Note'': WA3DSP wrote a [https://hamvoip.org/downloads/node-ban-allow.sh menu script] for the above commands.
 ==Blacklist Configuration==

@@ Line 5: / Line 5: @@
 ** <code>*CLI> database put blacklist 1998 "any comment"</code>
 ** <code>*CLI> database del blacklist 1998</code>
-** database show blacklist
+** <code>*CLI> database show blacklist</code>
 * Whitelist
-** database put whitelist 1000 "any comment"
+** <code>*CLI> database put whitelist 1000 "any comment"</code>
-** database del whitelist 1000
+** <code>*CLI> database del whitelist 1000</code>
-** database show whitelist
+** <code>*CLI> database show whitelist</code>
 *Both
-** database show
+** <code>*CLI> database show</code>
 ''Note'': WA3DSP [https://hamvoip.org/downloads/node-ban-allow.sh menu script] for above commands.