Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Antonio Quartulli]

Hi,

On 18/03/2019 22:30, tincanteksup wrote:
> Hi,
> 
> this situation has been hanging around for so long is this brief note
> really enough? Considering that the manual has numerous other URLs why
> not include this URL here:
> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
> 
> We already have this:
> https://community.openvpn.net/openvpn/wiki/SWEET32
> 

the problem with URLs is that they become obsolete and we need to
re-patch the manual in order to update them (or ensure the URL always
work/redirect to something).


However, I was thinking that a WARNING in the log when parsing a
dhcp-option without any script configured (on non-windows platform) may
also be beneficial.

Not many people will read it, but at least it will be there to be seen
at the first attempt of understanding what's wrong.

What do you think?

This said, the warning could/should be implemented as a separate patch.

Regards,

-- 
Antonio Quartulli



signature.asc
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH applied] Re: travis-ci: change trusty image to xenial

[Gert Doering]

Hi,

On Tue, Mar 19, 2019 at 01:18:37AM +0500,  ?? wrote:
> can we apply it to 2.4 as well ?
> ubuntu trusty is EOL soon

Steffan ACKed merging it into 2.4 as well.  For brevity I squashed the
three commits to the same file into one, which is appended below.

gert

-- 
"If was one thing all people took for granted, was conviction that if you 
 feed honest figures into a computer, honest figures come out. Never doubted 
 it myself till I met a computer with a sense of humor."
 Robert A. Heinlein, The Moon is a Harsh Mistress

Gert Doering - Munich, Germany g...@greenie.muc.de
From 6a5c9bb146061e3331a9000405c84150c8bad310 Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin 
Date: Mon, 11 Mar 2019 18:36:18 +0500
Subject: [PATCH] travis-ci: add "linux-ppc64le" to build matrix, change trusty
 image to xenial, update osx to xcode9.4 and modernize brew management

Signed-off-by: Ilya Shipitsin 
Acked-by: Steffan Karger 
Message-Id: <20190311133620.18278-2-chipits...@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg18271.html
Signed-off-by: Gert Doering 
(cherry picked from commit 27fb43da6f86eda7a6e5a033e060cab5be0cdbe9)

Ubuntu Trusty reaches End of Life on April 30, 2019
Let us switch to xenial. Also, it simplifies mingw builds.
We do not need to add xenial mingw manually anymore

Signed-off-by: Ilya Shipitsin 
Acked-by: Steffan Karger 
Message-Id: <20190311133620.18278-3-chipits...@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg18270.html
Signed-off-by: Gert Doering 
(cherry picked from commit 4ca813798af89997441bc35723ed1995b6b269e1)

osx image used for builds, i.e. xcode7.3 is outdated, we
can switch to "default" xcode9.4 and use more fast brew
travis-ci plugin

Signed-off-by: Ilya Shipitsin 
Acked-by: Steffan Karger 
Message-Id: <20190311133620.18278-4-chipits...@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg18269.html
Signed-off-by: Gert Doering 
(cherry picked from commit 2cae16aae55dd1ef2ae41c36bec752db34ab4695)
---
 .travis.yml   | 21 -
 .travis/build-deps.sh |  9 -
 2 files changed, 8 insertions(+), 22 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 62587d28..d7aff06e 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,5 +1,5 @@
 sudo: required
-dist: trusty
+dist: xenial
 
 os: linux
 
@@ -33,6 +33,9 @@ matrix:
 - env: SSLLIB="openssl" OPENSSL_VERSION="1.1.0f"
   os: linux
   compiler: gcc
+- env: SSLLIB="openssl" OPENSSL_VERSION="1.1.0h" LABEL="linux-ppc64le"
+  os: linux-ppc64le
+  compiler: gcc
 - env: SSLLIB="openssl" CFLAGS="-fsanitize=address"
   os: linux
   compiler: clang
@@ -47,11 +50,9 @@ matrix:
   compiler: clang
 - env: SSLLIB="openssl"
   os: osx
-  osx_image: xcode7.3
   compiler: clang
 - env: SSLLIB="mbedtls"
   os: osx
-  osx_image: xcode7.3
   compiler: clang
 - env: SSLLIB="openssl" CHOST=x86_64-w64-mingw32 OPENSSL_VERSION="1.0.1u"
   os: linux
@@ -76,12 +77,10 @@ matrix:
 
 addons:
   apt:
-packages:
-  - liblzo2-dev
-  - libpam0g-dev
-  - liblz4-dev
-  - linux-libc-dev
-  - man2html
+update: true
+packages: [ liblzo2-dev, libpam0g-dev, liblz4-dev, linux-libc-dev, man2html, mingw-w64]
+  homebrew:
+packages: [ lzo ]
 
 cache:
   directories:
@@ -89,10 +88,6 @@ cache:
   - ${HOME}/opt
   - ${HOME}/Library/Caches/Homebrew
 
-before_install:
-  - if [ "${TRAVIS_OS_NAME}" = "osx" ]; then brew update ; fi
-  - if [ "${TRAVIS_OS_NAME}" = "osx" ]; then brew install lzo; fi
-
 install:
   - if [ ! -z "${CHOST}" ]; then unset CC; fi
   - .travis/build-deps.sh > build-deps.log 2>&1 || (cat build-deps.log && exit 1)
diff --git a/.travis/build-deps.sh b/.travis/build-deps.sh
index 96a030cc..391b35ef 100755
--- a/.travis/build-deps.sh
+++ b/.travis/build-deps.sh
@@ -130,15 +130,6 @@ build_openssl () {
 fi
 }
 
-if [ ! -z ${CHOST+x} ]; then
-  #
-  # openvpn requires at least mingw-gcc-4.9, which is available at xenial repo
-  #
-  sudo apt-add-repository "deb http://archive.ubuntu.com/ubuntu xenial main universe"
-  sudo apt-get update
-  sudo apt-get -y install dpkg mingw-w64
-fi
-
 # Download and build crypto lib
 if [ "${SSLLIB}" = "openssl" ]; then
 download_openssl
-- 
2.18.0



signature.asc
Description: PGP signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

[Openvpn-devel] Summary of the community meeting (20th Mar 2019)

[Samuli Seppänen]

Hi,

Here's the summary of the IRC meeting.

---

COMMUNITY MEETING

Place: #openvpn-meeting on irc.freenode.net
Date: Wednesday 20th March 2019
Time: 11:30 CET (10:30 UTC)

Planned meeting topics for this meeting were here:



The next meeting has not been scheduled yet.

Your local meeting time is easy to check from services such as



SUMMARY

cron2, dazo, janjust, mattock, ordex, plaisthos and syzzer participated
in this meeting.

--

Discussed the OpenVPN T-shirts. Mattock has them but has
(unsurprisingly) been extremely slow in starting the shipping process.
Fortunately there's a deadline which mattock needs to meet [for a big
chunk of the shirts] and that deadline is quickly approaching.

If you've been promised a T-shirt and you have not sent your postal
address to mattock: please sent it now.

--

Discussed the Windows MSI PR in openvpn-build:

https://github.com/OpenVPN/openvpn-build/pull/141

Mattock will try out the cures to the tar.exe problem suggested by Selva
and report back. Once that problem is fixed everyone seems to feel
comfortable with merging the PR.

--

Discussed the Travis-CI base OS update PR:

https://github.com/OpenVPN/openvpn-build/pull/149

No obvious problems were spotted in it and mattock merged it during the
meeting.

--

Discussed tap-windows6 HLK testing / WHQL certification. Not much has
happened: we're close, but not there yet. Stephen said he'd be able to
pick up pace soon.

Some internal pressure is building up at OpenVPN Inc. because right now
we're prevented from building new tap-windows6 versions, even for
trivial reasons like changing the driver name as seen by Windows.

Mattock is leaning towards setting up a dedicated HLK testing
environment in-house, as outsourcing the testing would probably involve
considerable overhead (plus considerable fixed costs for each release/OS
combination). Also, we'd need to understand the test setup in order to
document it for the outsourcing company. Mattock will reopen discussions
about getting a Windows Server 2016 box for this purpose.

--

Discussed the current meeting schedule, which seems to be suboptimal for
some. Ordex will create a Doodle poll to understand what options we have.

--

Discussed our OpenVPN 2.5 patch backlog. People are trying to pick up
pace, but that has proven to be quite difficult.

--

Full chatlog attached.


(12:28:46) L'argomento di #openvpn-meeting è: Next meeting on 13/Feb/2019 at 
11:30CET. Agenda at https://community.openvpn.net/openvpn/wiki/Topics-2019-02-13
(12:28:46) L'argomento per #openvpn-meeting è stato impostato da 
ordex!~linux...@open-mesh.org/batman/ordex a 11:35:02 su 13/02/2019
(12:30:56) ordex: meeting ?
(12:31:00) mattock: yes
(12:31:06) ***syzzer present :)
(12:31:15) mattock: hi syzzer and ordex!
(12:32:17) janjust [~janjust@openvpn/community/support/janjust] è entrato nella 
stanza.
(12:32:48) syzzer: hi mattock1 :)
(12:32:55) janjust: hi all
(12:33:06) ordex: hi
(12:33:11) ordex: dazo said will be a bit late
(12:33:44) mattock: do we have our leader, cron2? :P
(12:33:48) janjust: hi mattock1 , just a quick question before we start: I've 
not received the hackathon t shirt yet. did you send it already?
(12:34:27) mattock: no, I have been shamefully slow
(12:34:34) mattock: but I do have a deadline and it is almost here
(12:34:40) janjust: no problem :)
(12:34:56) janjust: I just wanted to know if I should start badgering some 
postal people 
(12:35:15) ordex: mattock1: does it mean you will send the first day after the 
deadline ?
(12:35:15) ordex: :D
(12:35:30) ordex: oh I have an address in EU if you want to send something to 
me too :-P
(12:35:36) janjust: hehe
(12:35:56) mattock: ordex: you're absolutely correct there! :D
(12:36:02) cron2_: ho
(12:36:03) cron2_: sorry
(12:36:06) mattock: I will postpone until I have to send the T-shirts with 
super-express-fast mail
(12:36:09) mattock: :P
(12:36:13) cron2_: got stuck in a meeting
(12:36:16) janjust: yo syzzer , btw: I am still digging into that 'auth token 
before payload' question. The *spec* might state that it is sent first, but I 
cannot find it in the *code*
(12:36:47) janjust: mattock1, just do a world tour to drop by each of us 
individually with a gift-wrapped shirt
(12:36:51) mattock: https://community.openvpn.net/openvpn/wiki/Topics-2019-03-20
(12:36:52) vpnHelper: Title: Topics-2019-03-20 – OpenVPN Community (at 
community.openvpn.net)
(12:37:11) janjust: hiya cron2_ 
(12:37:16) mattock: janjust: that's an idea :)
(12:37:34) janjust: most expensive hackathon t shirt ever :)
(12:37:36) ***cron2_ sees syzzer and ordex - cool :)
(12:37:48) mattock: added one topic to the list
(12:37:55) mattock: anything to add to the topic list?
(12:38:30) janjust: I've got something I'd like to discuss, but could be done 
on the devel list also
(12:38:48) ordex: list looks good to me
(12:39:13) ordex: I just have an update on tran

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Selva Nair]

Hi,

On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:
>
> Hi,
>
> On 18/03/2019 22:30, tincanteksup wrote:
> > Hi,
> >
> > this situation has been hanging around for so long is this brief note
> > really enough? Considering that the manual has numerous other URLs why
> > not include this URL here:
> > https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
> >
> > We already have this:
> > https://community.openvpn.net/openvpn/wiki/SWEET32
> >
>
> the problem with URLs is that they become obsolete and we need to
> re-patch the manual in order to update them (or ensure the URL always
> work/redirect to something).


I have the same opinion about URLs. On top of that the wiki
description is inadequate and inaccurate. But that's a different
topic.

The patch was meant to remove the ambiguity in the current
wording. We could add a line saying many distributions include
such scripts and front-ends such as network manager, tunnelblick,
OpenVPN for Android etc. also handle some dhcp-options. (I don't use
any of them, so guessing here..)

>
>
> However, I was thinking that a WARNING in the log when parsing a
> dhcp-option without any script configured (on non-windows platform) may
> also be beneficial.

This would catch some obvious cases but not when a script is being
used for some other purpose. Still, sounds useful.

Selva


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Arne Schwabe]

Am 20.03.19 um 14:25 schrieb Selva Nair:
> Hi,
> 
> On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:
>>
>> Hi,
>>
>> On 18/03/2019 22:30, tincanteksup wrote:
>>> Hi,
>>>
>>> this situation has been hanging around for so long is this brief note
>>> really enough? Considering that the manual has numerous other URLs why
>>> not include this URL here:
>>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
>>>
>>> We already have this:
>>> https://community.openvpn.net/openvpn/wiki/SWEET32
>>>
>>
>> the problem with URLs is that they become obsolete and we need to
>> re-patch the manual in order to update them (or ensure the URL always
>> work/redirect to something).
> 
> 
> I have the same opinion about URLs. On top of that the wiki
> description is inadequate and inaccurate. But that's a different
> topic.
> 
> The patch was meant to remove the ambiguity in the current
> wording. We could add a line saying many distributions include
> such scripts and front-ends such as network manager, tunnelblick,
> OpenVPN for Android etc. also handle some dhcp-options. (I don't use
> any of them, so guessing here..)
> 

Yes. Most platforms and client interpret this option. Only OpenVPN
itself only interprets it only Windows and Android. It should probably
changed to reflect reality.

Arne


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[tincanteksup]

On 20/03/2019 13:25, Selva Nair wrote:

Hi,

On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:


Hi,

On 18/03/2019 22:30, tincanteksup wrote:

Hi,

this situation has been hanging around for so long is this brief note
really enough? Considering that the manual has numerous other URLs why
not include this URL here:
https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients

We already have this:
https://community.openvpn.net/openvpn/wiki/SWEET32



the problem with URLs is that they become obsolete and we need to
re-patch the manual in order to update them (or ensure the URL always
work/redirect to something).



I have the same opinion about URLs. On top of that the wiki
description is inadequate and inaccurate. But that's a different
topic.


Inadequate:
Compared to NOTHING, the page is at least a step toward documentation.

Inaccurate:
Please expand ..



___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Selva Nair]

Hi,

On Wed, Mar 20, 2019 at 9:45 AM Arne Schwabe  wrote:
>
> Am 20.03.19 um 14:25 schrieb Selva Nair:
> > Hi,
> >
> > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:
> >>
> >> Hi,
> >>
> >> On 18/03/2019 22:30, tincanteksup wrote:
> >>> Hi,
> >>>
> >>> this situation has been hanging around for so long is this brief note
> >>> really enough? Considering that the manual has numerous other URLs why
> >>> not include this URL here:
> >>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
> >>>
> >>> We already have this:
> >>> https://community.openvpn.net/openvpn/wiki/SWEET32
> >>>
> >>
> >> the problem with URLs is that they become obsolete and we need to
> >> re-patch the manual in order to update them (or ensure the URL always
> >> work/redirect to something).
> >
> >
> > I have the same opinion about URLs. On top of that the wiki
> > description is inadequate and inaccurate. But that's a different
> > topic.
> >
> > The patch was meant to remove the ambiguity in the current
> > wording. We could add a line saying many distributions include
> > such scripts and front-ends such as network manager, tunnelblick,
> > OpenVPN for Android etc. also handle some dhcp-options. (I don't use
> > any of them, so guessing here..)
> >
>
> Yes. Most platforms and client interpret this option. Only OpenVPN
> itself only interprets it only Windows and Android. It should probably
> changed to reflect reality.

In case of Android, its only sent to the management, right? As the man
page is about
OpenVPN core, I would say the current statement that the option is
handled only on
Windows is correct.

But its useful to expand on the usage on other platforms. I can add a
line about scripts in OS
distributions and front-ends/UI like Android that can transparently handle it.

Selva


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Selva Nair]

On Wed, Mar 20, 2019 at 10:52 AM tincanteksup 
wrote:
>
>
>
> On 20/03/2019 13:25, Selva Nair wrote:
> > Hi,
> >
> > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:
> >>
> >> Hi,
> >>
> >> On 18/03/2019 22:30, tincanteksup wrote:
> >>> Hi,
> >>>
> >>> this situation has been hanging around for so long is this brief note
> >>> really enough? Considering that the manual has numerous other URLs why
> >>> not include this URL here:
> >>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
> >>>
> >>> We already have this:
> >>> https://community.openvpn.net/openvpn/wiki/SWEET32
> >>>
> >>
> >> the problem with URLs is that they become obsolete and we need to
> >> re-patch the manual in order to update them (or ensure the URL always
> >> work/redirect to something).
> >
> >
> > I have the same opinion about URLs. On top of that the wiki
> > description is inadequate and inaccurate. But that's a different
> > topic.
>
> Inadequate:
> Compared to NOTHING, the page is at least a step toward documentation.
>
> Inaccurate:
> Please expand ..

The wiki states that on Windows using version 2.4, OpenVPN-GUI+interactive
service required for processing this option. Not so.
Just as in 2.3, it works if run as admin. In fact, several setups run
OpenVPN on boot using OpenVPNService, and --dhcp-option does work for them.
With 2.4, it also works as limited user if started using the interactive
service (for example, using OpenVPN-GUI).

In both 2.3 and 2.4, the critical piece is not overriding --ipwin32 method
(adaptive or dynamic is required and the latter is the
default).

Selva


On Wed, Mar 20, 2019 at 10:52 AM tincanteksup 
wrote:

>
>
> On 20/03/2019 13:25, Selva Nair wrote:
> > Hi,
> >
> > On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:
> >>
> >> Hi,
> >>
> >> On 18/03/2019 22:30, tincanteksup wrote:
> >>> Hi,
> >>>
> >>> this situation has been hanging around for so long is this brief note
> >>> really enough? Considering that the manual has numerous other URLs why
> >>> not include this URL here:
> >>> https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients
> >>>
> >>> We already have this:
> >>> https://community.openvpn.net/openvpn/wiki/SWEET32
> >>>
> >>
> >> the problem with URLs is that they become obsolete and we need to
> >> re-patch the manual in order to update them (or ensure the URL always
> >> work/redirect to something).
> >
> >
> > I have the same opinion about URLs. On top of that the wiki
> > description is inadequate and inaccurate. But that's a different
> > topic.
>
> Inadequate:
> Compared to NOTHING, the page is at least a step toward documentation.
>
> Inaccurate:
> Please expand ..
>
>
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[Arne Schwabe]

> 
> In case of Android, its only sent to the management, right? As the man
> page is about
> OpenVPN core, I would say the current statement that the option is
> handled only on
> Windows is correct.

Well everything is just to managment on Android, even opening the tun
device. But Android and Win32 are the two platforms on which the core
parses the DNS option and explicity calls functions to set a DNS server.

Arne


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[tincanteksup]

bonjour

On 20/03/2019 17:25, Selva Nair wrote:

On Wed, Mar 20, 2019 at 10:52 AM tincanteksup 
wrote:




On 20/03/2019 13:25, Selva Nair wrote:

Hi,

On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  wrote:


Hi,

On 18/03/2019 22:30, tincanteksup wrote:

Hi,

this situation has been hanging around for so long is this brief note
really enough? Considering that the manual has numerous other URLs why
not include this URL here:
https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients

We already have this:
https://community.openvpn.net/openvpn/wiki/SWEET32



the problem with URLs is that they become obsolete and we need to
re-patch the manual in order to update them (or ensure the URL always
work/redirect to something).



I have the same opinion about URLs. On top of that the wiki
description is inadequate and inaccurate. But that's a different
topic.


Inadequate:
Compared to NOTHING, the page is at least a step toward documentation.

Inaccurate:
Please expand ..


The wiki states that on Windows using version 2.4, OpenVPN-GUI+interactive
service required for processing this option. Not so.


I am actively promoting 2.4 use, I am not re-writing the manual.


Just as in 2.3, it works if run as admin. In fact, several setups run
OpenVPN on boot using OpenVPNService, and --dhcp-option does work for them.
With 2.4, it also works as limited user if started using the interactive
service (for example, using OpenVPN-GUI).


I am actively demoting 2.3 use, I am not re-writing the manual.


In both 2.3 and 2.4, the critical piece is not overriding --ipwin32 method
(adaptive or dynamic is required and the latter is the
default).



I am actively promoting the use of the Interactive Service.
I am not rewriting the manual ..

If a problem arises from using Openvpn as the page describes then,
depending on the cause, a resolution can be pursued ..

thanks
tct



___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[tincanteksup]

bonjour

On 20/03/2019 08:00, Antonio Quartulli wrote:

Hi,

On 18/03/2019 22:30, tincanteksup wrote:

Hi,

this situation has been hanging around for so long is this brief note
really enough? Considering that the manual has numerous other URLs why
not include this URL here:
https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients

We already have this:
https://community.openvpn.net/openvpn/wiki/SWEET32



Reinserted from my original post:

Please consider adding it.





the problem with URLs is that they become obsolete and we need to
re-patch the manual in order to update them (or ensure the URL always
work/redirect to something).


However, I was thinking that a WARNING in the log when parsing a
dhcp-option without any script configured (on non-windows platform) may
also be beneficial.

Not many people will read it, but at least it will be there to be seen
at the first attempt of understanding what's wrong.

What do you think?



The argument against using URLs in the Manual has these facts to refute:
* URLs are already in use in the manual
* I cited another example of using a URL in the manual.
* Some URLS in use in the manual are external to openvpn.net
* Using URLs in online documentation is The standard practice.
* There are even URLs in the Openvpn log files ..

It is easier to maintain linked documentation than it is to have to
patch the source so, given that the link is under the openvpn.net wing,
this seems perfectly reasonable to me.


Adding a warning for this problem in the log file is unsuitable:
* When the situation changes the source will have to be maintained.
* The situation will change.
* It is easier to maintain linked documentation to account for change.
* Log files are for diagnosing problems and should not have any URLs..
(Except for one URL to ${help}.openvpn, a URL which is unlikely to 
change and can therefore be easily maintained by OpenVPN Inc and remove

that burden from the FOSS Openvpn development team)

my2c thanks
tct




This said, the warning could/should be implemented as a separate patch.

Regards,




___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

[Openvpn-devel] Doodle: day/time for next weekly community meetings

[Antonio Quartulli]

Hi all,

As mentioned today on IRC, I have prepared a doodle to help us choose
when to schedule the next community meetings.

The doodle targets next week, but the idea is to choose a time slot that
is good "from now on".

The meeting duration is still fixed to 1 hour.

Please, fill the doodle with your votes by Sunday (March 24th, 2019)
night, so that on Monday morning Samuli can send out the invitation with
the elected day/time.

Link: https://doodle.com/poll/qbnsw7d4mvb5iysn#calendar

Thanks!

-- 
Antonio Quartulli



signature.asc
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[tincanteksup]

On 20/03/2019 18:12, tincanteksup wrote:

bonjour

On 20/03/2019 17:25, Selva Nair wrote:

On Wed, Mar 20, 2019 at 10:52 AM tincanteksup 
wrote:




On 20/03/2019 13:25, Selva Nair wrote:

Hi,

On Wed, Mar 20, 2019 at 4:02 AM Antonio Quartulli  
wrote:


Hi,

On 18/03/2019 22:30, tincanteksup wrote:

Hi,

this situation has been hanging around for so long is this brief note
really enough? Considering that the manual has numerous other URLs 
why

not include this URL here:
https://community.openvpn.net/openvpn/wiki/Pushing-DNS-to-clients

We already have this:
https://community.openvpn.net/openvpn/wiki/SWEET32



the problem with URLs is that they become obsolete and we need to
re-patch the manual in order to update them (or ensure the URL always
work/redirect to something).



I have the same opinion about URLs. On top of that the wiki
description is inadequate and inaccurate. But that's a different
topic.


Inadequate:
Compared to NOTHING, the page is at least a step toward documentation.

Inaccurate:
Please expand ..


The wiki states that on Windows using version 2.4, 
OpenVPN-GUI+interactive

service required for processing this option. Not so.


I am actively promoting 2.4 use, I am not re-writing the manual.


Just as in 2.3, it works if run as admin. In fact, several setups run
OpenVPN on boot using OpenVPNService, and --dhcp-option does work for 
them.

With 2.4, it also works as limited user if started using the interactive
service (for example, using OpenVPN-GUI).


I am actively demoting 2.3 use, I am not re-writing the manual.

In both 2.3 and 2.4, the critical piece is not overriding --ipwin32 
method

(adaptive or dynamic is required and the latter is the
default).



I am actively promoting the use of the Interactive Service.
I am not rewriting the manual ..

If a problem arises from using Openvpn as the page describes then,
depending on the cause, a resolution can be pursued ..

thanks
tct



This thread was _initially_ about pushing DNS to Linux clients.




___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] [PATCH] Improve the documentation for --dhcp-option

[tincanteksup]

Correcion

>From: Selva Nair 
>
>Make clear that --dhcp-option is not processed on
>non-Windows clients


This thread was _initially_ about pushing DNS to Linux clients.


I mean "non-windows" clients.




___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel