Date: Tue, 1 Sep 2020 18:00:11 -0500 From: Dustin Marquess <dmarquess@gmail.com> To: Jason Tubnor <jason@tubnor.net> Cc: Hiroshi Nishida <nishida@asusa.net>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: IPv6 Problem with Bhyve Message-ID: <CAJpsHY4PnWJEUVHsFDZynCev=_kvpaC2QfwEurQ3KivDzuPK2Q@mail.gmail.com> In-Reply-To: <CACLnyCKKZMiV5070JAHThxvrpqD0vRdysVnihNzkt3F=NGHqtA@mail.gmail.com> References: <53835548-cd6e-6859-c19d-8dd96d3993f3@asusa.net> <0b2304fd-4799-f56e-2271-169a5348d654@asusa.net> <CACLnyCKKZMiV5070JAHThxvrpqD0vRdysVnihNzkt3F=NGHqtA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 1, 2020 at 5:11 PM Jason Tubnor <jason@tubnor.net> wrote: > > On Wed, 2 Sep 2020 at 00:20, Hiroshi Nishida <nishida@asusa.net> wrote: > I hit similar bugs in various ways around IPv6 guests in 12.0 with > lingering problems in 12.1. All issues appeared to be fixed in 12-STABLE > now, so 12.2 should be good to go. Can you test 12-STABLE snapshot if > possible? The issue wasn't necessarily around bhyve, but more iflib. > > Interestingly, I have exactly the same problem also with CentOS 8 + > > KVM/QEMU. > > > > > ^^^ This is interesting, maybe it isn't bhyve or a FreeBSD issue at play > here if you are also getting it under KVM. We have a high count of Windows > 2019 Server bhyve guests in our environment, but they are running on 11.4 > and no IPv6 so I'm not going to be much use in being able to reproduce > this. I'll work on getting IPv6 working on my home connection and drag a > W2k19 image home, but this will take a while as I have other pressing work > commitments. I have Server 2019 VMs under bhyve (FreeBSD-CURRENT) using both static IPv6 and SLAAC IPv6, and I have no problems at all connecting to them using RDP over IPv6. Are you absolutely sure the Windows firewall is set to wide open? -Dustin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJpsHY4PnWJEUVHsFDZynCev=_kvpaC2QfwEurQ3KivDzuPK2Q>