Fixing wg-quick's DNS= directive with a hatchet
Jason A. Donenfeld
Jason at zx2c4.com
Fri Oct 27 19:15:08 CEST 2017
On Fri, Oct 27, 2017 at 5:38 PM, Joe Doss <joe at solidadmin.com> wrote:
> Don't let small amount of WG users that are rude and ignorant push the
> project around. It's not the project's fault that they don't understand how
> to install resolvconf or manage their own DNS if wg-quick doesn't work. This
> isn't me saying that we shouldn't make it better. We should and we will. It
> is just going to take time.
Actually, the problem is that there's no resolvconf of any kind on
Fedora, and this is what wg-quick uses. Thus wg-quick doesn't work
with Fedora, yet we ship packages for Fedora with wg-quick. So:
there's a problem that we need to work out. I take responsibility for
it and I don't blame the users.
> If you feel this is super important and you want to ship a hacky solution to
> fix then do it.
> It's a temp solution for a problem that needs a lot more packaging and dev
> time to fix correctly for every distro.
Alright. So in that case, I guess ship the hatchet as a patch in the
RPM, and later when you have time, you can investigate if there's
actually a proper Fedora way of doing things. Likewise Martin can do
the same with OpenSUSE.
(Daniel and Egbert seem mostly okay with the butchered resolvconf in
their distros; at least they don't see any reason to change things,
since it mostly works, and users there at least have the choice of
somehow installing openresolv need be.)
> manage my own DNS because I don't have a fancy NetworkManager drop down in
> GNOME to do it for me... at least not yet. ;)
Sounds like a fun project coming up...
> With that all said, I don't think the hatchet solution is great.
> have this issue fixed because users are super frustrated then do it for
> now and we can fix it later with the right way to do things in Fedora.
I suppose that's the plan then!
More information about the WireGuard