From owner-freebsd-bugs@freebsd.org Tue Oct 1 13:21:23 2019 Return-Path: Delivered-To: freebsd-bugs@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 ECA3E13655B for ; Tue, 1 Oct 2019 13:21:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46jKfW625Kz3MMS for ; Tue, 1 Oct 2019 13:21:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CEEA313655A; Tue, 1 Oct 2019 13:21:23 +0000 (UTC) Delivered-To: bugs@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 CEAE7136559 for ; Tue, 1 Oct 2019 13:21:23 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46jKfW56zNz3MMR for ; Tue, 1 Oct 2019 13:21:23 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7C1A31BF97 for ; Tue, 1 Oct 2019 13:21:23 +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 x91DLNkM001568 for ; Tue, 1 Oct 2019 13:21:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x91DLNjl001532 for bugs@FreeBSD.org; Tue, 1 Oct 2019 13:21:23 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: bugs@FreeBSD.org Subject: [Bug 240969] [netinet6] neighbour reachability detection broken when using multiple FIB Date: Tue, 01 Oct 2019 13:21:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: topical@gmx.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2019 13:21:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240969 Bug ID: 240969 Summary: [netinet6] neighbour reachability detection broken when using multiple FIB Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: topical@gmx.net If you define multiple FIB and set "net.add_addr_allfibs=3D0", ND reachabil= ity packets are sent via wrong interface, containing wrong data. Effectively: * reachability detection only works in FIB 0 * neighbour routers/firewalls may barf about strange ND packets for other FIBs (this is what happens to me) Still, network connectivity recovers automatically as standard ND multicasts are sent out automatically after reachability detection fails. After some investigation, I found the source of the problem: review D1998 introduced FIB-aware nd6_ns_output_fib() and a legacy wrapper nd6_ns_output= () passing RT_DEFAULT_FIB unconditionally. So, all calls to nd6_ns_output() mu= st be enhanced by FIB and replaced by calls to nd6_ns_output_fib().=20 As nd6_ns_output() is enclosed by "#ifndef BURN_BRIDGES", this seems to be = the original intention, but work has never been finished. --=20 You are receiving this mail because: You are the assignee for the bug.=