From nobody Tue Oct 05 09:35:06 2021 X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D124112D803D for ; Tue, 5 Oct 2021 09:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HNsrB5MFnz4gHS for ; Tue, 5 Oct 2021 09:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 956DE2146 for ; Tue, 5 Oct 2021 09:35:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1959Z6An048755 for ; Tue, 5 Oct 2021 09:35:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1959Z6ZL048754 for net@FreeBSD.org; Tue, 5 Oct 2021 09:35:06 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: net@FreeBSD.org Subject: [Bug 243554] multicast packets not seen on PHY bridge member Date: Tue, 05 Oct 2021 09:35:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pmh@hausen.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243554 --- Comment #9 from Patrick M. Hausen --- > 4. User should REMOVE IP from igb0 and ADD IP to the bridge (does not hav= e one by default) Yes! Yes! Yes! All IP addresses MUST be on the bridge interface and not on any member. FreeNAS/TrueNAS has been doing it wrong for years. The problem is with dynamically generated bridge interfaces of course. Most TrueNAS users won't notice, because there is not much in IPv4 that rel= ies on multicast. So it works, most of the time. With IPv6 things get interesti= ng ... If you plan to use VNET jails or VMs with tap and bridge, best practice is = to statically create the bridge at boot time via cloned_interfaces and configu= re IP accordingly. Then point your VM/jail orchestration tool at the existing bridge instead of having it create a new one. > > [ ... statement by Kristof ...] > Can you point me to this? Private conversation, but you can of course just ask him. That single statement in the handbook essentially says it all - but by far = not prominently enough, IMHO. Kind regards, Patrick --=20 You are receiving this mail because: You are the assignee for the bug.=