Re: [Openvpn-devel] [openvpn-devel] Forum upgrade problems

Here is an example of something which does not currently work with the default prosilver overlay. https://forums.openvpn.net/viewtopic.php?f=1&t=24917 On 19/09/17 15:39, Eric F Crist wrote: Switching the forum back from our custom style to the prosilver default resolves at least the [code] BB

[Openvpn-devel] Summary of community meeting (Wed, 20th Sep 2017)

Hi, Here's the summary of today's IRC meeting. --- COMMUNITY MEETING Place: #openvpn-meeting on irc.freenode.net Date: Wednesday 20th Sep 2017 Time: 19:00 CET (17:00 UTC) Planned meeting topics for this meeting were here: The n

Re: [Openvpn-devel] [openvpn-devel] Forum upgrade problems

I want to add, you don't have to include the =name part of the code. The BBCode will work just fine with [oconf]foo[/oconf]. --- Eric F Crist On 2017-09-20 05:39, fragmentux wrote: Another suggestion: Can you please change [oconf=x] to simply [oconf] There is enough remaining information to

Re: [Openvpn-devel] Better error recognition and error/status reporting to the mgmt i/f

Hello, I beleive that people will ignore "not green" status. I think there're should be an option of treating that situation as fatal error. However, I agree that it requires help from core 20 сент. 2017 г. 8:39 ПП пользователь "Selva" написал: > Hi, > > On Thu, Sep 14, 2017 at 3:21 PM, Selva

Re: [Openvpn-devel] [openvpn-devel] Forum upgrade problems

I’m not going to make that change. Eric Crist > On Sep 20, 2017, at 5:39 AM, fragmentux wrote: > > Another suggestion: > Can you please change [oconf=x] to simply [oconf] > There is enough remaining information to be able to determine what > the config is used for .. and if there isn't then a

Re: [Openvpn-devel] Better error recognition and error/status reporting to the mgmt i/f

Hi, On Thu, Sep 14, 2017 at 3:21 PM, Selva wrote: > Hi, > > Quoting from the meeting logs: > > >> Discussed having more fine-grained signalling from OpenVPN to OpenVPN >> GUI. The lack of clear signals from OpenVPN to OpenVPN GUI has been a >> rather common problem: >> > > >>

Re: [Openvpn-devel] [PATCH v2] Check whether in pull_mode before warning about previous connection blocks

Hi, On Fri, Sep 15, 2017 at 2:46 PM, wrote: > From: Selva Nair > > In particular, this eliminates the message that says "explicit-exit-notify > is ignored by previous blocks" when the option is pushed. > > Note: pull_mode is identified as "allowed & OPT_P_PULL_MODE" matching with > the > defin

Re: [Openvpn-devel] Solaris 11: t_lpback.sh coredump on AES-GCM

>Hello. > >Spent a day debugging this issue on OpenIndiana. >If anyone steps on this once again... >It seems the issue was caused OI/Solaris OpenSSL specific patches, in >particular by >https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/library/openssl/openssl-1.0. 2/patches/0

Re: [Openvpn-devel] [openvpn-devel] Forum upgrade problems

Another suggestion: Can you please change [oconf=x] to simply [oconf] There is enough remaining information to be able to determine what the config is used for .. and if there isn't then a simple question can be asked to clarify. Otherwise, people just use it blindly and assume it does not work.

Re: [Openvpn-devel] Solaris 11: t_lpback.sh coredump on AES-GCM

Hello. Spent a day debugging this issue on OpenIndiana. If anyone steps on this once again... It seems the issue was caused OI/Solaris OpenSSL specific patches, in particular by https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/library/openssl/openssl-1.0.2/patches/036-evp_l