Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Note in README the possibility to use on a separate host #9

Merged
merged 2 commits into from
Mar 25, 2024
+4 −1
Merged

Note in README the possibility to use on a separate host #9

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9531d96
Update README.md
kzemek Mar 25, 2024
ab66b8a
Update README.md
kzemek Mar 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,12 @@ 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 interface<sup>1</sup>;
- as root or with `CAP_NET_ADMIN` capability to be able to set `IP_TRANSPARENT` socket opt.

<sup>1</sup> 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

### Routing setup
Expand Down
Loading