From 9531d96bdd198b13a12a7babf26c4babd532e9d1 Mon Sep 17 00:00:00 2001 From: Konrad Zemek Date: Mon, 25 Mar 2024 17:07:42 +0100 Subject: [PATCH 1/2] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1865b7d..716062a 100644 --- a/README.md +++ b/README.md @@ -22,9 +22,11 @@ See [Go's Getting Started](https://golang.org/doc/install) if your package manag `go-mmproxy` has to be ran: -- on the same server as the proxy target, as the communication happens over the loopback interface; +- on the same server as the proxy target, as the communication happens over the loopback interface1; - as root or with `CAP_NET_ADMIN` capability to be able to set `IP_TRANSPARENT` socket opt. +1 This is not a hard requirement, and with routing magic go-mmproxy can be ran on a different host than the target(s). + ## Running ### Routing setup From ab66b8a3749a49cf4c3ad7b27402ead8a57e29d0 Mon Sep 17 00:00:00 2001 From: Konrad Zemek Date: Mon, 25 Mar 2024 17:09:12 +0100 Subject: [PATCH 2/2] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 716062a..581a6c0 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,7 @@ See [Go's Getting Started](https://golang.org/doc/install) if your package manag - as root or with `CAP_NET_ADMIN` capability to be able to set `IP_TRANSPARENT` socket opt. 1 This is not a hard requirement, and with routing magic go-mmproxy can be ran on a different host than the target(s). +See the [docker-example directory](https://github.com/kzemek/go-mmproxy/tree/main/docker-example) for a working example. ## Running