Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matteo Franzil <matteofranzil@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: wg-quick down not reverting DNS parameters on MacOS
Date: Mon, 24 Jul 2023 07:29:31 +0200	[thread overview]
Message-ID: <7cde2e10-b27d-0502-1b97-bacdbd9dd4a4@gmail.com> (raw)
In-Reply-To: <7522f2c6-5782-25f5-6f25-75d05d50b868@gmail.com>

Hi!

I extensively searched for any discussion on this bug (or at least, I 
hope so), which has been bugging me for a while.

I am a Wireguard user on macOS Ventura (version 13.4.1 (c)), and 
installed wireguard via the wireguard-tools (version 1.0.20210914) and 
wireguard-go (0.0.20230223) commands on brew.

Assume I have set my DNS servers either via GUI or via DHCP (doesn't 
matter how), and I use wg-quick to connect to a wg conf file (also 
irrelevant what is the target server).

The moment I:
- use wg-quick to bring up the VPN,
- put my Mac to sleep,
- reopen the lid,
- use wg-quick to stop the VPN,

then DNS servers are not updated back to the original value, and instead 
stick to what the previous VPN configuration had commanded.

The workaround is just to verify what DNS servers are set with scutil 
--dns and cat /etc/resolv.conf, but editing them is a pain. I often work 
with an open VPN and closing the lid without remembering to turn it of 
is common.

Let me know if I also need to provide further details.

See also this GitHub issue, which was posted on an unrelated repository 
but perfectly matches what I have just said:

https://github.com/StreisandEffect/streisand/issues/1334


Matteo


       reply	other threads:[~2023-08-23 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7522f2c6-5782-25f5-6f25-75d05d50b868@gmail.com>
2023-07-24  5:29 ` Matteo Franzil [this message]
2023-08-10 14:50   ` Matteo Franzil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7cde2e10-b27d-0502-1b97-bacdbd9dd4a4@gmail.com \
    --to=matteofranzil@gmail.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).