Crates.io | cproxy |
lib.rs | cproxy |
version | 4.1.6 |
source | src |
created_at | 2021-02-24 04:42:23.58298 |
updated_at | 2021-10-25 07:19:04.760775 |
description | Transparent proxy built on cgroup net_cls. |
homepage | https://github.com/NOBLES5E/cproxy |
repository | |
max_upload_size | |
id | 359804 |
size | 78,023 |
cproxy
can redirect TCP and UDP traffic made by a program to a proxy, without requiring the program supporting a
proxy.
What you can achieve with cproxy
: All the things listed on for
example V2Ray Guide, including advanced configurations like reverse porxy
for NAT traversal, and you can apply different proxy on different applications.
Compared to many existing complicated transparent proxy setup, cproxy
usage is as easy as proxychains
, but
unlike proxychains
, it works on any program (including static linked Go programs) and redirects DNS requests.
Note: The proxy used by cproxy
should be a transparent proxy port (such as V2Ray's dokodemo-door
inbound and
shadowsocks ss-redir
). A good news is that even if you only have a SOCKS5 or HTTP proxy, there are tools that can
convert it to a transparent proxy for you (for example, transocks
, ipt2socks and ip2socks-go).
You can install by downloading the binary from the release page or
install with cargo
:
cargo install cproxy
chown root:root $(which cproxy) && chmod +s $(which cproxy)
proxychains
You can launch a new program with cproxy
with:
cproxy --port <destination-local-port> -- <your-program> --arg1 --arg2 ...
All TCP connections requests will be proxied. If your local transparent proxy support DNS address overriding, you can
also redirect DNS traffic with --redirect-dns
:
cproxy --port <destination-local-port> --redirect-dns -- <your-program> --arg1 --arg2 ...
For an example setup, see wiki.
If your system support tproxy
, you can use tproxy
with --mode tproxy
:
cproxy --port <destination-local-port> --mode tproxy -- <your-program> --arg1 --arg2 ...
# or for existing process
cproxy --port <destination-local-port> --mode tproxy --pid <existing-process-pid>
With --mode tproxy
, there are several differences:
tproxy
enabled on the inbound port. For V2Ray, you
need "tproxy": "tproxy"
as
in V2Ray Documentation. For shadowsocks, you
need -u
as shown in shadowsocks manpage.An example setup can be found here.
Note that when you are using the tproxy
mode, you can override the DNS server address
with cproxy --mode tproxy --override-dns <your-dns-server-addr> ...
. This is useful when you want to use a different
DNS server for a specific application.
With cproxy
, you can even proxy an existing process. This is very handy when you want to proxy existing system
services such as docker
. To do this, just run
cproxy --port <destination-local-port> --pid <existing-process-pid>
The target process will be proxied as long as this cproxy
command is running. You can press Ctrl-C to stop proxying.
With cproxy
, you can easily debug a program's traffic in netfilter. Just run the program with
cproxy --mode trace <your-program>
You will be able to see log in dmesg
. Note that this requires a recent enough kernel and iptables.
cproxy
creates a unique cgroup
for the proxied program, and redirect its traffic with packet rules.
cproxy
requires root access to modify cgroup
.There are some awesome existing work:
graftcp
also has performance hit on the underlying program, since it uses ptrace
.cgproxy
also uses cgroup to do transparent proxy, and the idea is
similar to cproxy
's. There are some differences in UX and system requirements:
cgproxy
requires system cgroup
v2 support, while cproxy
works with both v1 and v2.cgproxy
requires a background daemon process cgproxyd
running, while cproxy
does not.cgproxy
requires tproxy
, which is optional in cproxy
.cgproxy
can be used to do global proxy, while cproxy
does not intended to support global proxy.