Date: Fri, 26 Oct 2018 12:05:30 +0200 From: Andrea Venturoli <ml@netfence.it> To: Harry Schmalzbauer <freebsd@omnilan.de>, freebsd-virtualization@freebsd.org Subject: Re: Network identification problem with Windows 10 on bhyve Message-ID: <76ae92a5-4ade-8798-d584-eba2ccf35709@netfence.it> In-Reply-To: <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de> References: <0de2dbf1-bb31-e10b-777b-b93d6ca92683@netfence.it> <8cad7f22-946c-915d-c6e4-a55d682e9f29@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76ae92a5-4ade-8798-d584-eba2ccf35709>