AdguardTeam / AdguardTeam/AdGuardVPNCLI

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

Open
#67 1 comment 0 reactions 1 assignee Claimed by @sfionov View on GitHub
Bug Priority: P4 Version: VPN CLI v2.0
Dominant language
Shell
Stars
209
Forks
15
PR merge metrics
No merged PRs in 30d

Description

### Please answer the following question for yourself before submitting an issue

- [X] 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_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.