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

Routing adguardvpn-cli internet connection to other docker containers doesn't fully mask local ISP IP #67

Open
1 task done
mjeshurun opened this issue Oct 22, 2024 · 1 comment
Assignees
Labels

Comments

@mjeshurun
Copy link

Please answer the following question for yourself before submitting an issue

  • I checked to make sure that this issue has not already been filed

AdGuard VPN CLI version

1.1.126

Environment

  • OS: Adguardvpn-cli installed as a docker container on Unraid

Issue Details

Steps to reproduce:

  1. login to adguardvpn-cli
  2. connect vpn
  3. run with TUN and Adguard DNS enabled
  4. route vpn traffic to qbittorrent docker container
  5. test qbittorrent ip using ipleak.net
  6. ipleak.net torrent magnet test finds adguardvpn-cli servers IP address and also my local ISP IP address.

Expected Behavior

ipleak.net torrent magent test should only find adguardvpn-cli servers IP address.

Actual Behavior

ipleak.net torrent magnet test finds adguardvpn-cli servers IP address and also my local ISP IP address.

Screenshots

Screenshot 1

Additional Information

No response

@mjeshurun mjeshurun added the Bug Something isn't working label Oct 22, 2024
@mjeshurun
Copy link
Author

Here is a screenshot taken from ipleak.net

Screenshot 2024-10-22 at 20 20 25

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

No branches or pull requests

3 participants