On Wed, May 10, 2017 at 2:47 PM, ValdikSS <valdi...@gmail.com> wrote:
>
> Windows 10 before Creators Update used to resolve DNS using all
> available adapters and IP addresses in parallel. Now it still
> resolves addresses using all available adapters but in a round-robin
> way, beginning with random adapter.
> This behaviour introduces significant delay when block-outside-dns is
> in use. Fortunately, setting low metric for the TAP interface solves
> this issue, making Windows always pick TAP adapter first and disable
> round-robin.
> ---
> src/openvpn/block_dns.c | 78 ++++++++++++++++++++++++++++++
> +++++++++++++
> src/openvpn/block_dns.h | 30 +++++++++++++++++
> src/openvpn/init.c | 4 +--
> src/openvpn/win32.c | 39 ++++++++++++++++++++--
> src/openvpn/win32.h | 2 +-
> src/openvpnserv/interactive.c | 70 +++++++++++++++++++++++++++++++++++---
> 6 files changed, 213 insertions(+), 10 deletions(-)
Looks good now. ACK from me.
Did a quick test on Win7 -- metric changes to 3 and gets restored
independently for v4 and v6. No idea whether this resolves the Win 10 issue,
but should not have any adverse effects except for the metric change
which will also affect the metric of routes added.
Cross compiles without issues for 32 bit and 64 bit -- tested on Debain 8.7
with
mingw32-w64 included in the distribution.
Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
