From owner-freebsd-virtualization@freebsd.org Fri Oct 26 07:45:46 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 00B7310DA319 for ; Fri, 26 Oct 2018 07:45:46 +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 5C3376AFBB for ; Fri, 26 Oct 2018 07:45:44 +0000 (UTC) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id w9Q7GwsW053565 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 26 Oct 2018 09:17:05 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu From: Andrea Venturoli Subject: Network identification problem with Windows 10 on bhyve To: freebsd-virtualization@freebsd.org Message-ID: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it> Date: Fri, 26 Oct 2018 09:16:58 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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 07:45:46 -0000 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. This has the unpleasant consequence that some services won't run (or actually will run, but won't be reachable) between a reboot and me manually connecting. Is anyone else seeing this? Know how to solve? bye & Thanks av.