[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-03 Thread Dan Streetman
Uploaded patched systemd to b/c queues. -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-03 Thread Dan Streetman
** Tags added: ddstreet-next -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression To manage notifications about this bug go to:

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-03 Thread Dan Streetman
** Also affects: network-manager (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: syst

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-03 Thread Dan Streetman
> Is this going to be fixed in disco? speaking for systemd only, the commit needed is a97a3b256cd6c56ab1d817440d3b8acb3272ee17: https://github.com/systemd/systemd/commit/a97a3b256 that's included starting at v240, so is already in disco. -- You received this bug notification because you are a

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-05 Thread Dan Streetman
@dwmw2 and/or @till-kamppeter, can you verify the systemd upload for this bug for b and c? -- You received this bug notification because you are a member of Network- manager, which is subscribed to NetworkManager. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-06-18 Thread Dan Streetman
This was fixed in systemd 237-3ubuntu10.22 for bionic, and 239-7ubuntu10.14 for cosmic. I missed a "#" in the changelog (sorry) so the tooling didn't automatically mark this bug as fix released. ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in:

[Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-08-03 Thread Dan Streetman
> In benchmarking we didn't observe much computational difference between the too once the CPU is fully loaded. However, cranking up or cranking down the load one will discover that the performance setting is more responsive than powersave. this is exactly the problem in production environments;

[Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-08-03 Thread Dan Streetman
> I would suggest switching back to powersave/ondemand either with a new service or the kernel config. re: new service, the existing package cpufrequtils (and related package cpufreqd) provides a configurable service to manage governor settings (and other related settings). The old ondemand