From owner-freebsd-virtualization@freebsd.org  Fri Oct 26 10:05:36 2018
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF7D710DDCC5
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Fri, 26 Oct 2018 10:05:35 +0000 (UTC) (envelope-from ml@netfence.it)
Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it
 [2.44.121.52])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "mailserver.netfence.it",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 553226F6F6
 for <freebsd-virtualization@freebsd.org>; Fri, 26 Oct 2018 10:05:35 +0000 (UTC)
 (envelope-from ml@netfence.it)
Received: from guardian.ventu (host-219-49.248-87.enter.it [87.248.49.219]
 (may be forged)) (authenticated bits=0)
 by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w9QA5THG072455
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
 Fri, 26 Oct 2018 12:05:30 +0200 (CEST) (envelope-from ml@netfence.it)
X-Authentication-Warning: soth.netfence.it: Host host-219-49.248-87.enter.it
 [87.248.49.219] (may be forged) claimed to be guardian.ventu
Subject: Re: Network identification problem with Windows 10 on bhyve
To: Harry Schmalzbauer <freebsd@omnilan.de>, freebsd-virtualization@freebsd.org
References: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it>
 <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de>
From: Andrea Venturoli <ml@netfence.it>
Message-ID: <76ae92a5-4ade-8798-d584-eba2ccf35709@netfence.it>
Date: Fri, 26 Oct 2018 12:05:30 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.83
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2018 10:05:36 -0000

On 10/26/18 10:03 AM, Harry Schmalzbauer wrote:

> Have you checked inside the guest that it really uses the defined MAC 
> with the interface?

Yes, IPCONFIG /ALL shows the MAC address I specificed in the vmbhyve 
config file.



> Other than that I don't have an idea.  Gateway MAC is also taken into 
> account by Windows NetworkListManager...

I'm trying sysctl net.link.bridge.inherit_mac=1, to see if it makes any 
difference.
I'll also check and see if the tap adapter MAC address changes over reboots.

Thanks.

  bye
	av.