search

mullvad / mullvadvpn-app

The Mullvad VPN client app for desktop and mobile
https://mullvad.net/
GNU General Public License v3.0
4.99k stars 334 forks source link

Connected to wireguard but showing a different ip location #1876

Closed Disrooting closed 2 years ago

Disrooting commented 4 years ago

Issue report

Operating system: Windows 10

App version: Latest

Issue description

connected to denmark using wireguard, i did an ip leak test and it shows that the main ipv4 is sweden and the proxy is denmark. if you want to check that yourself just connect to a denmark location using wireguard then go to https://ipleak.net and it will show up that you are in two locations Mullvad_VPN_07puYlUUod . i hope you find this helpful.

pronebird commented 4 years ago

Hi,

Is it possible that you have WebRTC enabled in your browser and it leaks your real IP?

Please test with https://am.i.mullvad.net as well.

Normally you should contact support and not Github (developers) for such matters. If you keep seeing this issue, please ping our support via the app or website and they should help you with resolving this or register the case, that we will be able to resolve asap in the order of priority.

Cheers, Andrej

Disrooting commented 4 years ago

I can confirm that it isn't related to WebRTC, but rather wireguard itself. No matter what location i choose to connect to, it always shows that the IPV4 is in sweden and the IPV6 is the location i chose to connect to. I had to change to OpenVPN to check if it is indeed a WebRTC problem, but it turns out it wasn't. you can see that with OpenVPN i'm connected to the right location and it shows both ways IPV4 & IPV6 as well as the DNS Mullvad_VPN_V4JYQwew7L

I hope this would help you guys investigate the problem

stefan-mullvad commented 4 years ago

Hi,

You can check the geolocation here: https://am.i.mullvad.net

If it shows correctly on our site but not ipleak.net then it's because they are not using the same geolocation database. It happens that there are inconsistencies between databases, and it can take some time before they get the correct information.

Best regards, Stefan

faern commented 2 years ago

I'm closing this due to inactivity. The results to Stefan's request to verify the leak with our own leak check tool was never reported. If we leak it's serious. But I don't see any proofs that we do currently. Feel free to re-open if this is still an issue.