Introduced custom protocols with IP and (optional) port support

Example

- Single IP address
  ip:213.75.170.11@CustomProtocol

- IP address with CIDR
  ip:213.75.170.11/32@CustomProtocol

- IP address with CIDR and port
  ip:213.75.170.11/32:443@CustomProtocol

Please note that there are some restrictions on the port
usage. They have been listed in example/protos.txt

1 files changed, 19 insertions, 0 deletions

diff --git a/example/protos.txt b/example/protos.txt
index ef9d2ffac..b472d27f9 100644
--- a/example/protos.txt
+++ b/example/protos.txt
@@ -17,6 +17,25 @@ host:"api-global.netflix.com"@Netflix
 #  Format:
 #  ip:<value>,ip:<value>,.....@<subproto>
 
+#
+# NOTES
+# 1) the port of a custom protocol is optional but if
+#    specified it must match the port.
+# 2) you can specify up to 1 port per IP address
+# 3) if you specify a custom ip:<IP>:<PORT> rule,
+#    even if the <PORT> doesn't match the <IP>
+#    (if best match during the search) will
+#    have priority as best match. Example if
+#    you specify a <Google IP>:<port 9999> and
+#    in your traffic have match for such IP but
+#    with a port other than 9999, the IP address
+#    begin a best match will hve preference over
+#    <Google IP> so this protocol will not be
+#    detected as <L7 proto>.Google but only
+#    as <L7 proto>
+#
+
 ip:213.75.170.11/32:443@CustomProtocol
 ip:8.248.73.247:443@AmazonPrime
 ip:54.80.47.130@AmazonPrime
+