From nobody Thu May 30 02:54:01 2024 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 4VqW6f6JH3z5Ltcj for ; Thu, 30 May 2024 02:54:02 +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 4VqW6f4pLRz4TKs for ; Thu, 30 May 2024 02:54:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717037642; a=rsa-sha256; cv=none; b=OGit+85JWKCD0N/ikub9vRIAhdotOGtihxyCaG63nRxbGWY4Od9islK2JCvepXT74vNrIZ it9+Wex1TDG9g+LTFij4vAZAxefWBc1pNrQbm2V9rz5yu9zAZs3buBCDekz6eabXxxYGqs 1MEk9VEiAHLOlAgTsUmkLgxnSJsGg8IxcExx3Cdp+3mXM2PmtVzC6gdxrz4dlUfhv8gsB1 Uk87cr6jeiA0luwodhGlhL6bQ29y69ZFAkF63nuKH2j49a4JymWMGFsnnb/aBPVD+le8DR Nn5OSmPYKwJmeov+AZKW51xlp7q4P/rJjC1LapzlAlZtkAEPMHps4NLSw0YYXA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717037642; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Rlq3QNBYM+YBs5pFAvZKF90/Rci9DDDbcp/xOvrDR4Y=; b=VqfcIrHUe6yEFB3eeMlTLqKCwfRbphBmYnMovPhtF3TeSJG75K/Dx7h/ZtSmCxe85SVZeW y8iFX3cfdzf12GMhRZm7PclnOCynUhtXyMNEWRvJnapWA44ZKqhYrdy5fq+9Ay62wAphAY e/ZNCRxUyqct7exJE/BiCN6pnJLa0NghDs6GtQ7Ou3QPws160NgcDof5hhA/+PpTy4tI+b HigGh9rLxuuV0wF5xlkpFPxXFWdYCogoZqex9s5qElQgCconQoeVj2tbd3+Bzd7adRn+KI 3mX8P2ZNfNpD6BQ0KFwQX7PqhPavC7Hi+CoMYuwIgbbqnwC/Pk4/cPN3q1DQ8w== 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 4VqW6f47kmzND4 for ; Thu, 30 May 2024 02:54:02 +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 44U2s27w015161 for ; Thu, 30 May 2024 02:54:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 44U2s2pD015160 for net@FreeBSD.org; Thu, 30 May 2024 02:54:02 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 263288] IPv6 system not responding to Neighbor Solicitation Date: Thu, 30 May 2024 02:54:01 +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: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rblayzor@inoc.net 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263288 --- Comment #21 from Robert Blayzor --- I have run into this issue now a few times. I have seen hosts try to ping my IPv6 hosts from off network and they just hang. Upon investigation I have f= ound that the host is hung up on ignoring NS messages from the router, even thou= gh on the host we have NDP entries for both the link local and the global IP address. ie: # ndp -an | grep lagg1 | grep 00:09:0f 2607:f058:xx::1 00:09:0f:09:00:01 lagg1 23h34m17s S R fe80::209:fff:fe09:1%lagg1 00:09:0f:09:00:01 lagg1 23h33m53s S R PCAP shows NS messages from the router, but there is zero response, the host just ignores them. No firewall enabled at all.... I can ping from other hosts on the same subnet, that seems to work. The kicker is, if I ping6 FROM the host to the router it takes about 5 seco= nds (give or take) and then you're able to ping the gateway again. Once this happens, packets from remote are able to ping and traffic flows again. If I stop sending traffic and let things sit for about a minute, the process repeats again. NDP sol messages from the router are ignored again and remain broken until I ping the router from the host again. If I keep a continuous ping from a host off link, it will never fail. This seems to be some type of NDP timeout/cache issue. I have tried setting: net.inet6.icmp6.nd6_onlink_ns_rfc4861=3D1. but that d= oes not seem to solve the problem. I am currently seeing this on 13.1-RELEASE-p9 which is on a TrueNAS host. W= hile I realize 13.3 is current, TrueNAS seems to lag a little behind. I do have other TrueNAS hosts running this version that don't seem to experience this issue. (at least I've not reliably reproduced it on other machines) I have tried just rebooting the host, but I CAN reliably reproduce this iss= ue. I have no other ND issues from the router to other hosts on this network. I have confirmed the host *is* receiving the NS messages; it just never repli= es.. --=20 You are receiving this mail because: You are the assignee for the bug.=