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

Add ability to proxy based on destination IP rather than App #1697

Open
samthesamman opened this issue Sep 14, 2024 · 3 comments
Open

Add ability to proxy based on destination IP rather than App #1697

samthesamman opened this issue Sep 14, 2024 · 3 comments

Comments

@samthesamman
Copy link

I want to be able to send all 10.0.0.0/8 to my home wireguard network while everythng else to my 3rd party VPN wireguard network.

@ignoramous
Copy link
Collaborator

ignoramous commented Sep 14, 2024

This should already happen if a Peer's Allowed IPs is set to 10.0.0.0/8 for WireGuard running in both Advanced and Simple modes. Is that not what you see?

@ignoramous
Copy link
Collaborator

(closing... feel free to reopen)

@ignoramous ignoramous closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2024
@ignoramous ignoramous reopened this Oct 28, 2024
@ignoramous
Copy link
Collaborator

Use case is as follows. I would like to route all traffic (including all DNS-traffic, since my DNS server is within this range) within a certain private IP range via Wireguard to my router at home, primarily to access my home server. I would also like to use a commercial VPN to hide my IP for all IPs outside of above mentioned ip range. This should happen for the same apps. Theoretically I could achieve this by routing everything first to my home network, then everything not meant for my home network to the commercial VPN via policy-based routing configured in my home router. Problem is, this would give high latency, slow speed and is cumbersome. It would be better to directly split tunnel within the RethinkDNS app, depending on IP range, for example with two Wireguard configuration files, each with their own interface and peer, but with non-overlapping "Allowed IPs".

#1724

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

No branches or pull requests

2 participants