From 84f66b4d6b69d2e5a98d446d70e028d6fa560413 Mon Sep 17 00:00:00 2001 From: Luca Deri Date: Wed, 6 May 2020 12:51:44 +0200 Subject: 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 --- example/protos.txt | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'example') 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:,ip:,.....@ +# +# 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:: rule, +# even if the doesn't match the +# (if best match during the search) will +# have priority as best match. Example if +# you specify a : 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 +# so this protocol will not be +# detected as .Google but only +# as +# + ip:213.75.170.11/32:443@CustomProtocol ip:8.248.73.247:443@AmazonPrime ip:54.80.47.130@AmazonPrime + -- cgit v1.2.3