Hi,
On Fri, May 4, 2018 at 8:10 AM, Gert Doering <g...@greenie.muc.de> wrote:
> Hi,
>
> On Fri, May 04, 2018 at 12:26:54PM +0100, fragmentux wrote:
>> Perhaps an explanatory note in the manual would be appropriate ?
>
> No, spurious warnings just need to go.
>
> The point of the warning was: before 2.4, certain options applied globally,
> so "to all connection profiles", even if put in the config after all
> <connection> blocks.
>
> This was changed, so that these options could be set for some profiles
> and not for others (like, explicit-exit-notify) - but that implied that
> a 2.3 config
>
> <connection>
> ...
> </connection>
> <connection>
> ...
> </connection>
> explicit-exit-notify 3
>
>
> all of a sudden had *no* explicit-exit-notify configured anymore, instead
> of "for all profiles". Thus, warning.
>
> The warning is not relevant for pushed configs, so need to go.
This was fixed in 2.4.5:
commit 90812e9879ba47ff0275f20efd653ae3381308b8
Author: Selva Nair <selva.n...@gmail.com>
Date: Fri Sep 15 14:46:15 2017 -0400
Check whether in pull_mode before warning about previous connection blocks
Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
