Date: Fri, 13 Feb 2026 11:57:16 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 193246] Bug in IPv6 multicast join(), uncovered by Jenkins Message-ID: <bug-193246-7501-qNYBQ7SSrP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193246-7501@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193246 Bruce M Simpson <bms@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|--- |Normal URL| |https://reviews.freebsd.org | |/D55031 Severity|Affects Many People |Affects Some People --- Comment #20 from Bruce M Simpson <bms@FreeBSD.org> --- Just regained access after nearly a decade. There was some personal tragedy involved. The resolution for this is being tracked at: https://reviews.freebsd.org/D55031 With a minor errno correction at: https://reviews.freebsd.org/D55233 TL;DR This is purely an optional extension. It is not and never was a bug. The OpenJDK and other software started relying on it over the years, but it really doesn't fit with how the socket APIs involved were intended to operate, at all. It largely stems from uncertainty about the extent of IPv4-mapped address support, as tuexen has indicated. The cheap fix is to just do what Apple did and just pass it through to netinet for simple ASM-mode adds/joins, which is the most common multicast use case anyway, and it's usually for local link scoped groups. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193246-7501-qNYBQ7SSrP>