[Dnssec-trigger] [Bug] incorrect DNS servers are used when network-manager connects to VPN
Pavel Simerda
psimerda at redhat.com
Sun Sep 21 12:19:29 UTC 2014
----- Original Message -----
> From: "Ralf Jung" <post at ralfj.de>
> To: "Tomas Hozza" <thozza at redhat.com>, "Paul Wouters" <paul at nohats.ca>
> Cc: dnssec-trigger at NLnetLabs.nl, "Pavel Simerda" <psimerda at redhat.com>
> Sent: Sunday, September 21, 2014 12:06:31 PM
> Subject: Re: [Dnssec-trigger] [Bug] incorrect DNS servers are used when network-manager connects to VPN
>
> Hi,
>
> > As Paul said, there is an integration with NM if the VPN software exposes
> > necessary information to the NM. The information is then read using libnm
> > API from NM by dnssec-trigger hooks.
> >
> > I'm not a big fan of every VPN software re-configuring unbound on its
> > own. This is really bad approach and should not be used.
>
> Without knowing the technical details, I completely agree. It sounds
> like a bad hack.
>
> Do you have an example for a VPN plugin that uses the "right" way to
> expose information to NM? That would be a good starter to get this into
> OpenConnect.
There's https://git.gnome.org/browse/network-manager-openconnect/
Pavel
> Kind regards
> Ralf
>
More information about the dnssec-trigger
mailing list