From 08f180399ab6345a03aedadb23da3a1c6e8192c1 Mon Sep 17 00:00:00 2001
From: Jonathan Naylor <naylorjs@yahoo.com>
Date: Sat, 21 Jan 2017 19:14:25 +0000
Subject: [PATCH] Remove README.DMR_ACL

---
 README.DMR_ACL | 32 --------------------------------
 1 file changed, 32 deletions(-)
 delete mode 100644 README.DMR_ACL

diff --git a/README.DMR_ACL b/README.DMR_ACL
deleted file mode 100644
index a4eccc2..0000000
--- a/README.DMR_ACL
+++ /dev/null
@@ -1,32 +0,0 @@
-To use DMR Access Control you can add the following fields to your MMDVM.ini:
-
-Blacklist= <comma separated list of source-id's to block on RF>
-DstIdBlackListSlot1RF= <comma separated list TGs to block on RF Slot1>
-DstIdBlackListSlot2RF= <comma separated list TGs to block on RF Slot2>
-DstIdWhiteListSlot1RF= <comma separated list TGs to allow on RF Slot1> 
-DstIdWhiteListSlot2RF= <comma separated list TGs to allow on RF Slot2>
-DstIdBlackListSlot1NET= <comma separated list TGs to block on NET Slot1>
-DstIdBlackListSlot2NET= <comma separated list TGs to block on NET Slot2>
-DstIdWhiteListSlot1NET= <comma separated list TGs to allow on NET Slot1> 
-DstIdWhiteListSlot2NET= <comma separated list TGs to allow on NET Slot2>
-
-So, for example:
-
-DstIdBlackListSlot1=91 - block the TG91 net.
-
-DstIdWhiteListSlot1=9.5057,9990 - allows TG9, APRS SMS Gateway and Echo. 
-
-If the whitelist is null and commented out, it is disabled. 
-
-The whitelist behaves slightly differently on Slot1 than is does on Slot2.
-
-For Slot1, the whitelist will allow all IDs above 99999 and everything in the whitelist.
-
-For Slot2, the whitelist will allow all IDs between 4000 and 5000, IDs above 99999 and everything in the whitelist. 
-
-You can use the blacklist with the whitelist if you want to specifically block IDs within the allowed ranges above. 
-
-For example, to block users from disconnecting the reflectors, you could block ID 4000.
-
-To block users connecting to reflector 4400 you could add ID 4400 to the network blacklist for that slot. 
-