From: Alexander Joss <alexmjoss2413@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Recommended workaround for resolvconf bug
Date: Tue, 2 Mar 2021 15:43:43 -0800 [thread overview]
Message-ID: <CABqpv33QNdT17hZWfuYzc_rGmKgDfbf6iR0JAnp66BXvmfUknA@mail.gmail.com> (raw)
Hello list,
I recently moved into a new place and ran into the following issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904
Any recommendations for workarounds? I tried to create a symlink like
suggested in that thread which seemed to not work and also not exactly
happy about installing another package.
Also, I have no idea why I had no issues with the previous ISP. I no
longer have the old configuration, but I think they were pretty much
identical and didn't have any DNS field setup. Any ideas on why this
became a problem?
Alex
reply other threads:[~2021-03-03 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABqpv33QNdT17hZWfuYzc_rGmKgDfbf6iR0JAnp66BXvmfUknA@mail.gmail.com \
--to=alexmjoss2413@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).