mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
Transparent moved to main code (TransparentPlugin removed), BSD pf support added
(cherry picked from commit 88b3225bdf)
This commit is contained in:
1 parent
69c6ddc8c4
commit
da66016c7f
19 files changed
+972
-191
No files matched your search
@@ -1192,6 +1192,54 @@ the format:
|
||||
Note: double quotes are required because the password contains a $ sign.
|
||||
|
||||
.br
|
||||
.BR transparent
|
||||
\fI[auto|netfilter|pf|socket]\fR
|
||||
.br
|
||||
Take the destination of a connection, both address and port, from the packet
|
||||
filter that redirected it, instead of from the request. It applies to services declared after it, and
|
||||
\fBnotransparent\fR turns it off again for the services after that. Built into the
|
||||
binary since 1.0.1, and previously the separate TransparentPlugin.
|
||||
.br
|
||||
On Linux the kernel is asked, so \fBiptables\fR or \fBnftables\fR
|
||||
redirection is enough. On the BSDs pf is asked through \fB/dev/pf\fR, which
|
||||
3proxy must be able to read, so \fBrdr\fR rules work; a redirection that
|
||||
leaves the destination on the socket is used where there is one, as
|
||||
\fBdivert-to\fR on OpenBSD and \fBipfw fwd\fR on FreeBSD do. macOS ships no
|
||||
header for pf and has neither of those, so the commands exist in a macOS build
|
||||
but cannot be used.
|
||||
.br
|
||||
The mechanism is chosen automatically. The optional argument pins it for an
|
||||
installation that has more than one: \fBauto\fR is the default,
|
||||
\fBnetfilter\fR asks the Linux kernel, \fBpf\fR looks the connection up in
|
||||
the packet filter, and \fBsocket\fR reads the address off the socket. A mode
|
||||
the build has no code for is refused rather than ignored.
|
||||
.br
|
||||
A connection that reaches a \fBsocket\fR mode service without having been
|
||||
redirected is refused: its destination is the address the service listens on,
|
||||
and using that would send the service to itself.
|
||||
.br
|
||||
A redirected connection carries no destination of its own, so without this the
|
||||
service uses whatever it would use otherwise: the \fBHost\fR header for an
|
||||
HTTP request, or the address a port mapper was configured with. \fBtlspr\fR
|
||||
receives nothing at all unless traffic is redirected to it or the clients
|
||||
resolve names to it, and with a redirection it has the address as well as the
|
||||
name from the handshake, which is what allows access rules to be written with
|
||||
host names. With it, every service reaches the address the
|
||||
client was trying to reach, and access rules, parents, limits and logging apply
|
||||
to it as usual.
|
||||
.br
|
||||
The redirection rules must not match the connections the proxy itself makes to
|
||||
those destinations, or the traffic returns to the proxy and loops. Give the
|
||||
service an outgoing address with \fB-e\fR and exclude that address in the rules,
|
||||
or run 3proxy as its own user and exclude that user. See the
|
||||
.B TRANSPARENT PROXYING
|
||||
section of the documentation for rules per platform.
|
||||
.br
|
||||
.BR notransparent
|
||||
.br
|
||||
Stop taking the destination from the packet filter for the services declared
|
||||
after it.
|
||||
|
||||
.B flush
|
||||
.br
|
||||
empty the active access list. The access list must be flushed every time you create a
|
||||
|
||||
Reference in new issue
Block a user