From owner-freebsd-net@freebsd.org Fri Apr 23 05:57:12 2021 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BE2EC5E0AD0 for ; Fri, 23 Apr 2021 05:57:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FRNpw4cmGz3h3B for ; Fri, 23 Apr 2021 05:57:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 9CCCB5E08E5; Fri, 23 Apr 2021 05:57:12 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C9685E0ACE for ; Fri, 23 Apr 2021 05:57:12 +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 4FRNpw3zHhz3hM5 for ; Fri, 23 Apr 2021 05:57:12 +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 714F327D96 for ; Fri, 23 Apr 2021 05:57:12 +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 13N5vC5I081665 for ; Fri, 23 Apr 2021 05:57:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13N5vCuM081664 for net@FreeBSD.org; Fri, 23 Apr 2021 05:57:12 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 247912] [if_bridge] IPv6 ndp does not work across local bridge members Date: Fri, 23 Apr 2021 05:57:11 +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.2-RELEASE X-Bugzilla-Keywords: ipv6 X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at X-Bugzilla-Status: Open 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 MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Apr 2021 05:57:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247912 --- Comment #19 from Martin Birgmeier --- I'd like to come back to this issue. Basically, I am (still :-)) not assigning the IP addresses to the bridge interface. The major reason for this is that I am assembling/disassembling = the bridge and its member interfaces as needed, and I do not want to always hav= e to fiddle with reassigning IP addresses from the member interfaces to the brid= ge and vice versa. Which brings me to my point: In normal networking parlance a bridge knows nothing about ISO layer 3 and therefore not about IP. Much less it gets an = IP address assigned (let us not digress to smart managed devices). So I believe that we have a design issue here: In FreeBSD we are talking about a "bridge" but in reality it is kludge used to tie some interfaces together. Or at lea= st it is not a bridge in the traditional networking sense. How difficult would it be to redesign the bridge abstraction in FreeBSD to = more closely resemble a real layer 2 bridge? -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.=