[Openvpn-devel] [PATCH 3/4] Use netioapi instead of netsh to set mtu

--- src/openvpn/tun.c | 68 +++ src/openvpnserv/interactive.c | 44 +-- 2 files changed, 46 insertions(+), 66 deletions(-) diff --git a/src/openvpn/tun.c b/src/openvpn/tun.c index b0230a7c..9fe8444f 100644 --- a/src/openvpn/tun.c +++

[Openvpn-devel] [PATCH 1/4] Setting adapter mtu on windows systems

From: Christopher Schenk --- src/openvpn/tun.c | 39 ++- 1 file changed, 38 insertions(+), 1 deletion(-) diff --git a/src/openvpn/tun.c b/src/openvpn/tun.c index 48a8fdf7..93d028c8 100644 --- a/src/openvpn/tun.c +++ b/src/openvpn/tun.c @@ -69,6 +69,12 @@ stat

[Openvpn-devel] [PATCH 4/4] Simplified if statements for better readability

--- src/openvpn/tun.c | 58 --- 1 file changed, 14 insertions(+), 44 deletions(-) diff --git a/src/openvpn/tun.c b/src/openvpn/tun.c index 9fe8444f..20e661a7 100644 --- a/src/openvpn/tun.c +++ b/src/openvpn/tun.c @@ -69,7 +69,7 @@ static void netsh_ifco

[Openvpn-devel] [PATCH 2/4] Setting MTU also via interactive service

--- include/openvpn-msg.h | 8 + src/openvpn/tun.c | 67 ++- src/openvpnserv/interactive.c | 50 ++ 3 files changed, 124 insertions(+), 1 deletion(-) diff --git a/include/openvpn-msg.h b/include/openvpn-msg.h index 6

Re: [Openvpn-devel] [PATCH 3/4] Use netioapi instead of netsh to set mtu

Hi, On Mon, Apr 1, 2019 at 7:22 AM Christopher Schenk < csch...@mail.uni-paderborn.de> wrote: > --- > src/openvpn/tun.c | 68 +++ > src/openvpnserv/interactive.c | 44 +-- > 2 files changed, 46 insertions(+), 66 deletions(-) > > dif

Re: [Openvpn-devel] [PATCH 4/4] Simplified if statements for better readability

Hi, On Mon, Apr 1, 2019 at 7:22 AM Christopher Schenk < csch...@mail.uni-paderborn.de> wrote: > --- > src/openvpn/tun.c | 58 --- > 1 file changed, 14 insertions(+), 44 deletions(-) > @@ -213,7 +213,7 @@ do_set_mtu_service(const struct tuntap *tt, co

Re: [Openvpn-devel] [PATCH 4/4] Simplified if statements for better readability

Hi, On Mon, Apr 01, 2019 at 11:59:04AM -0400, Selva Nair wrote: > Finally, I'm not sure whether we still require patch authors to follow the > code formatting style or we automatically run uncrustify during merge. We have decided that all *core* authors are required to either run uncrustify or "g