Date: Mon, 16 Oct 2017 20:32:11 -0500 From: Lewis Donzis <lew@perftech.com> To: freebsd-net@FreeBSD.org Subject: Re: [Bug 221385] [Regression] v6 mapped v4 addresses not working in 11.1 Message-ID: <490283D6-C663-46BE-9125-CCD9C49CD0BF@perftech.com> In-Reply-To: <DFF7B75E-F590-4E15-9B6A-8E9B3BECD7FC@perftech.com> References: <bug-221385-2472@https.bugs.freebsd.org/bugzilla/> <bug-221385-2472-XvbDNlHGhJ@https.bugs.freebsd.org/bugzilla/> <DFF7B75E-F590-4E15-9B6A-8E9B3BECD7FC@perftech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Would appreciate some guidance on this. It seems like a reasonably = serious regression, so I=E2=80=99m surprised it hasn=E2=80=99t already = been fixed. Since all of our code binds a particular library, we were able to work = around it by overriding the weak referenced socket() with our own = version that creates the socket and explicitly turns off the V6ONLY = option, but that doesn=E2=80=99t help with third-party applications. Thanks, lew > On Sep 13, 2017, at 7:47 AM, Lewis Donzis <lew@perftech.com> wrote: >=20 > Hello. >=20 > This particular bug is a real problem in our embedded system, and = we=E2=80=99re trying to decide whether to go back to 11.0 or wait for a = patch for 11.1. >=20 > We downloaded just the one file containing the fix, but it wouldn=E2=80=99= t compile, so we downloaded -CURRENT and verified that it works fine. = But it=E2=80=99s unclear to me whether the code in -CURRENT is slated = for an 11.1 patch, or if it won=E2=80=99t show up until 11.2 or even = 12.0. I see the "mfc-stable11 = <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221385#h5>=E2=80=9D = flag on the bug set to a value of =E2=80=9C?=E2=80=9D. Is that = significant? >=20 > Perhaps someone can help us understand how to determine when and in = which version a fix will show up. >=20 > Thanks, > lew >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?490283D6-C663-46BE-9125-CCD9C49CD0BF>