From owner-freebsd-virtualization@freebsd.org Thu Nov 1 18:25:14 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 E380410FB04C for ; Thu, 1 Nov 2018 18:25:13 +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 2CD91847F4 for ; Thu, 1 Nov 2018 18:25:12 +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 wA1IOsHU005368 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 1 Nov 2018 19:25:02 +0100 (CET) (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 Subject: Re: Network identification problem with Windows 10 on bhyve From: Andrea Venturoli To: freebsd-virtualization@freebsd.org References: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it> <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de> <76ae92a5-4ade-8798-d584-eba2ccf35709@netfence.it> Message-ID: <15402830-012b-d482-4da4-b28e2871420c@netfence.it> Date: Thu, 1 Nov 2018 19:24:54 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <76ae92a5-4ade-8798-d584-eba2ccf35709@netfence.it> 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: Thu, 01 Nov 2018 18:25:14 -0000 On 10/26/18 12:05 PM, Andrea Venturoli wrote: > I'm trying sysctl net.link.bridge.inherit_mac=1, to see if it makes any > difference. It looks like this does the trick, although I'm not sure yet; however, it breaks other things. In fact, in order to get a more deterministic behaviour with ipfw, I have: net.link.bridge.pfil_bridge=0 net.link.bridge.pfil_local_phys=1 Having the same MAC address on the bridge and the physical interfaces doesn't allow incoming packet to be assigned to the correct one. > I'll also check and see if the tap adapter MAC address changes over > reboots. In fact tap0's MAC changes after every reboot. As soon as I have the chance, I'll try and see if I can fix this. bye av.