From owner-freebsd-virtualization@freebsd.org Fri Oct 26 08:04:02 2018 Return-Path: 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 3BA3010DAC4F for ; Fri, 26 Oct 2018 08:04:02 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3AD66B83B for ; Fri, 26 Oct 2018 08:04:01 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w9Q83xEt017048; Fri, 26 Oct 2018 10:03:59 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id EAC651B4; Fri, 26 Oct 2018 10:03:58 +0200 (CEST) Subject: Re: Network identification problem with Windows 10 on bhyve To: Andrea Venturoli , freebsd-virtualization@freebsd.org References: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it> From: Harry Schmalzbauer Organization: OmniLAN Message-ID: <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de> Date: Fri, 26 Oct 2018 10:03:58 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: ACL 130 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Fri, 26 Oct 2018 10:03:59 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2018 08:04:02 -0000 Am 26.10.2018 um 09:16 schrieb Andrea Venturoli: > Hello. > > I've got a FreeBSD 11.2/amd64 + vm-bhyve + Windows 10 pro. > I'm building the network bridge statically, i.e., I have the following > in /etc/rc.conf: >> cloned_interfaces="bridge0 tap0" >> ifconfig_bridge0="up addm igb0" > > I'm using virtio network drivers and I'm also fixing the MAC address; > i.e. I have the following in /zroot/vm/win10/win10.conf: >> network0_type="virtio-net" >> network0_switch="public" >> network0_mac="58:9c:fc:00:11:65" >> network0_device="tap0" > > The Windows machine is connected to an AD domain. > > > > Every time I reboot the server, Windows will think it is in a new > network: connecting to the box via RDP, a message will pop up asking > me whether I want the machine to be discoverable on "Network 1". > Next time I reboot and connect via RDP, it will ask about "Network 2"; > then "Network 3" and so on. Have you checked inside the guest that it really uses the defined MAC with the interface? Other than that I don't have an idea.  Gateway MAC is also taken into account by Windows NetworkListManager... Good luck, -harry