From owner-freebsd-bugs@freebsd.org Mon Jul 23 19:09:31 2018 Return-Path: Delivered-To: freebsd-bugs@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 B21EC1052AFA for ; Mon, 23 Jul 2018 19:09:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3F8F88A972 for ; Mon, 23 Jul 2018 19:09:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EF2811052AEB; Mon, 23 Jul 2018 19:09:30 +0000 (UTC) Delivered-To: bugs@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 B47A71052AEA for ; Mon, 23 Jul 2018 19:09:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E6258A971 for ; Mon, 23 Jul 2018 19:09:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 992ABD6F6 for ; Mon, 23 Jul 2018 19:09:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6NJ9TPV049148 for ; Mon, 23 Jul 2018 19:09:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6NJ9Tjg049147 for bugs@FreeBSD.org; Mon, 23 Jul 2018 19:09:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229990] FreeBSD 11.2 on Hyper-V: hn0: network changed, change 1 Date: Mon, 23 Jul 2018 19:09:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bazald@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 19:09:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229990 Bug ID: 229990 Summary: FreeBSD 11.2 on Hyper-V: hn0: network changed, change 1 Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bazald@gmail.com I am attempting to run FreeBSD 11.2 under Hyper-V on Windows 10 1803. I have tried both Gen 1 and Gen 2 virtual machines, as well as both legacy and non-legacy network adapters under Gen 1, and networking seems to be difficu= lt to get right, at least with Wi-Fi. The only configuration that seems to work at all is using a Gen 2 VM (non-legacy network adapter). I initially attempted to use a virtual switch configured to access the external network, with sharing allowed, and I quic= kly got MAC collision errors. I'm uncertain as to whether that's the expected result. Moving on to the default switch, sharing my Wi-Fi with that, I seem to have working Internet access. I added "net.link.ether.inet.max_age=3D60" to /etc/sysctl.conf, which seems to be important for maintaining the connectio= n. As a new FreeBSD user, it is distressing that https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/best= -practices-for-running-freebsd-on-hyper-v fails to document that it truly ought to be added to /etc/sysctl.conf. Finally, even with this apparently working connection, we get to the bug I'm actually here to report. I'm still getting flooded with "hn0: network chang= ed, change 1" messages on the terminal. The patch at https://reviews.freebsd.org/D8295 seems to be to blame? I believe NDIS_NETCHANGE_TYPE_POSSIBLE is being reported to the console, and perhaps correctly so given the networking issues with Hyper-V, but some method to at least suppress the messages would be most welcome. --=20 You are receiving this mail because: You are the assignee for the bug.=