References: <20170504173605.8269-1-valdikss@...277...> From: ValdikSS Message-ID: Date: Sat, 6 May 2017 00:28:54 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------FB9A2A6B333A0327171A32DF" Content-Language: en-GB Subject: Re: [Openvpn-devel] [PATCH] Set a low interface metric for tap adapter when block-outside-dns is in use List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Selva Nair Cc: "openvpn-devel@lists.sourceforge.net" This is a multi-part message in MIME format. --------------FB9A2A6B333A0327171A32DF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 05.05.2017 23:21, Selva Nair wrote: > Hi, > > On Thu, May 4, 2017 at 1:36 PM, ValdikSS > wrote: > > Hmm... If it starts with a random adapter, this metric lowering is not the right fix, isn't it? Or did you mean to say "starting from lowest metric adapter"? > > > Well, I'm looking for to excuses to avoid the hard work of a careful review :) If reducing metric is indeed the right approach in this cat and mouse game with MS, I'll try to look through this over the weekend. From what I understand, Windows tries to use DNS in a round-robin fashion if adapter's metric is set to automatic, regardless of computed metric value. If we disable automatic metric on TAP adapter and set it lower than computed metric of other adapters, it would be used first. I could be not completely correct with this, but I tested it and it works. > > 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 --------------FB9A2A6B333A0327171A32DF Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit On 05.05.2017 23:21, Selva Nair wrote:

Hi,

On Thu, May 4, 2017 at 1:36 PM, ValdikSS <valdikss@...277...> wrote:

Hmm... If it starts with a random adapter, this metric lowering is not the right fix, isn't it? Or did you mean to say "starting from lowest metric adapter"?

Well, I'm looking for to excuses to avoid the hard work of a careful review :) If reducing metric is indeed the right approach in this cat and mouse game with MS, I'll try to look through this over the weekend.

From what I understand, Windows tries to use DNS in a round-robin fashion if adapter's metric is set to automatic, regardless of computed metric value. If we disable automatic metric on TAP adapter and set it lower than computed metric of other adapters, it would be used first.
I could be not completely correct with this, but I tested it and it works.

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

--------------FB9A2A6B333A0327171A32DF--