-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
[Feature request] Gateway mode #126
Comments
I haven't test this case, let me check what is going wrong later. |
Thanks. I was just testing with the Zerotier custom route feature to enable cross-internet private IP access. Though the packet never entered v2ray-MARK. I guess there are some other rules accept that somewhere before |
I am not really familiar with netfliter things at all. Let me note why package from bridge device are not being redirected to tproxy server at now. Currently, cgtproxy will produce rules like:
check this:
For package not send via bridge or something like that, socket cgroupv2 will not take effect at all. It result that package not marked at all, which means a DIRECT. |
I see. My use case was using wireguard to proxy traffic to the central wireguard server and serve as a gateway. Though, as a kernel module, it does not really have a cgroup so that's probably why it doesn't work. Close for now. |
I think it is fine to have a default tproxy target when traffic doesn't have a cgroup, which is the "gateway mode" you wanted. I am finding ways to implement this feature. This might related to #79 |
Will
cgtproxy
supports gateway mode likecgproxy
have been? It is quite handy to deploy it on VPS and use the VPS to route client traffic. This would require gateway mode.The text was updated successfully, but these errors were encountered: