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

option to exclude other IPs from the VPN #2138

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

obito02
Copy link

@obito02 obito02 commented Aug 22, 2024

Enable the option to exclude other IP addresses from the VPN, since in my case I must route to 127.0.0.1 which causes the loopback address to be excluded, but not the VPN or the real IP. To do this, add an array that contains the extra IP addresses to be able to exclude from the VPN.

I want to clarify that this dependency is required to be added in order to use the IPNetwork2 class.
Dependency

@obito02 obito02 requested a review from a team as a code owner August 22, 2024 02:14
Copy link

google-cla bot commented Aug 22, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Collaborator

@fortuna fortuna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you clarify what you want to do? Do you want to send traffic addressed to 127.0.0.1 over to the remote server?

@obito02
Copy link
Author

obito02 commented Aug 27, 2024

Can you clarify what you want to do? Do you want to send traffic addressed to 127.0.0.1 over to the remote server?

I use it to route traffic in tun2socks or gotun2socks in SSH, I use bitvise that creates a socks 5 listening port at 127.0.0.1 and then if I use that route the real remote SSH server is not excluded which would not give me a connection, then by adding the possibility of excluding other IP addresses it allows me to connect to 127.0.0.1 where bitvise is in socks5 forward and thus tunnel, that's why I decided to share it since it could also be used in outline if in some cases you want to exclude other IP addresses from the tunnel

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

Successfully merging this pull request may close these issues.

2 participants