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.

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」Add support for redirecting traffic to user-specified interfaces #901

Closed
ple1n opened this issue Apr 2, 2023 · 1 comment
Labels
feature a whole new feature

Comments

@ple1n
Copy link

ple1n commented Apr 2, 2023

Besides deny and allow, it may redirect traffic to other interfaces. The purpose is to have a GUI-based solution to proxy-selective-routing on Linux, ie. selecting individual proxies for different applications, which is troublesome and inaccessible at this moment for most users. This feature should allow for greater privacy for an average user.

TUN interfaces may be created through tun2socks for socks proxies, including Tor, and lokinet creates TUN/TAP interface on its own. I know that 'redirecting to interfaces' might not be the best solution for the said goal. Maybe it'd possible to redirect the traffic to Opensnitch and dispatch it to corresponding socks proxies directly, according to the rules, basically incorporating tun2socks.

It'd even better to redirect DNS resolution, based on the same set of firewall rules. Ex. One application binary is resolved through a proxied DNS server.

@ple1n ple1n added the feature a whole new feature label Apr 2, 2023
@gustavo-iniguez-goya
Copy link
Collaborator

Closing as duplicated of #738 and #437, although with more details :)
I'll give it another try with new ideas once 1.6.0 is released. Let's keep discussing about this on #437

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a whole new feature
Projects
None yet
Development

No branches or pull requests

2 participants