Open TennesseePete opened 5 years ago
If I remember right wireguard does something like this when the allowed ips field doesn’t include ipv6, for example
AllowedIPs = 0.0.0.0/0 would leak AllowedIPs = 0.0.0.0/0, ::/0 wouldn’t leak So try setting allowed ips to the above in your client and see if it helps
I setup my own DNS using unbound on the VPS host, and direct all my wireguard peers to the gateway IP as the DNS server. I have tethered my laptop to my iOS mobile hotspot. Both devices have wireguard up and running. DNSleaktest shows my laptop is leaking (ISP = Mobile phone provider). However, running the leaktest through my iPhone browser (correctly) shows my VPS IP as the ISP--no leaks on the phone itself.
Expected behavior:
Laptop would also show my VPS IP as the DNS server.
Actual Behavior:
Laptop shows my mobile phone provider as the DNS.
Steps to Reproduce:
[ contents of
streisand-diagnostics.md
here ]Additional Details:
Log output from Ansible or other relevant services (link to Gist for longer output):
I spun up these wireguard peers manually w/o using Ansible
Target Cloud Provider:
Digital Ocean
Operating System of target host:
18.04
Operating System of client:
1) 18.04 2) iOS
*Version of Ansible, using
ansible --version
:N/A
Output from
git rev-parse HEAD
in your Streisand directory :