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

Linux DNS not being set as expected. #58

Open
bleach86 opened this issue May 25, 2024 · 1 comment
Open

Linux DNS not being set as expected. #58

bleach86 opened this issue May 25, 2024 · 1 comment

Comments

@bleach86
Copy link

Trying to run the client example with my values put in as required as well as adding a DNS configuration.

I notice that when it would connect I would not have internet access. I narrowed this down to a DNS issue caused by /etc/resolv.conf not being updated as expected.

Looking at wg-quick I notice that they prefix the interface name with tun..

So modifying configure_dns() and clear_dns() to do the same results in expected behavior of updating /etc/resolv.conf with my values.

The linux wg-quick man page as well as the freebsd wg-quick man page both indicate the same prefixing of the interface name with tun.

This could cause a DNS leak if you allow local networks in your wg config.

This would cause using unexpected DNS if you do not allow local networks, but your '/etc/resolv.conf` contains an IP of a remote host. This could also possibly be a leak as well.

To recreate be on Linux with a wg config with AllowedIPs = 0.0.0.0/0,::/0 and have only LAN IPs in /etc/resolv.conf

@teon
Copy link
Contributor

teon commented Jun 18, 2024

@bleach86 could you elaborate and explain what are you expecting from us?

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

No branches or pull requests

2 participants