Hi. On Mon, Jan 20, 2025 at 2:38 PM Heiko Hund <he...@openvpn.net> wrote:
> Hi Jon > > On Montag, 20. Januar 2025 00:02:46 CET Jonathan K. Bullard wrote: > > On Mon, Jan 13, 2025 at 8:13 AM d12fk (Code Review) <ger...@openvpn.net> > > wrote: > > > With --dns-script in place we no longer need DNS related vars in the > > > environment for other script hooks. Code for doing that is removed and > > > the function to set --dns stuff made static, for internal use only. > > > > > > Another thing: since --dns setting overrule DNS related --dhcp-options, > > > remove the latter when we got some via --dns. > > > > Does this mean that if there are --dns options which override > > --dns-options options, then (for macOS) the foreign_options_N > > environment variables related to DNS will not be passed to the up/down > > scripts? That would be a a *major* breaking change. > > Yes, that is the intended behavior. However, I'll port the macos DNS > setting > code from openvpn3 to a macos --dns-script for openvpn 2, which will run > automatically. DNS will not break this way, but depending on how the --up > script is written, that one might. I've not come up with an idea on how to > prevent this potential breakage, besides a warning in the release notes > unfortunately. > Thanks. That will impact Tunnelbllick because we set DNS in our own up/down scripts. But I understand the reasons for the change. Am I correct that the plan for this to go into 2.7 or later, and not into 2.6? Best regards, Jon
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
