From nobody Mon Apr 10 05:08:21 2023 X-Original-To: bugs@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 4Pvxnd2Q65z44mg7 for ; Mon, 10 Apr 2023 05:08:21 +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 4Pvxnd0nkYz3R86 for ; Mon, 10 Apr 2023 05:08:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681103301; 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=BLGgfvd7KKqbAZ4V1KJAVK2ZyT9mPv5ruwkvDeYJXsM=; b=AYrAylfcSck13xC1wk0kGIO9trYyg8FhNxLybvDfS+NqtCwDVqEtm2MTyvV03WKt+HeQTz Px83us6MPJg7Gq7fIldb4c8d0ohKnvbsqrOW0bDCnw5txkvieCWN0gYMSPXNqX2HrapKqt lPKxVZ/Ga04HZ6WMvTkW6376Zf7ExfIAAS/QhZr3HsEGvB9H89RNAbeIFr1Phk9PIx0W0C zwUuDD1tCqHIx0BiNtxtERbi2AhxESPGVCgDGZFuMsz+tajjP8KjfHd8zpQ0eRvr6R3Cpg LQ3e9EH1l4/9waB3E8RNYF6YUXevN2PxXJ6M+UBxm1K4ONGnBTcZjpHzvT5cpQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681103301; a=rsa-sha256; cv=none; b=qdpDNCIfL+8lLlG4o7loQOhG2cycD0pbVBox1Nti82R/0kFQWtJq61Z2nsr5DP/AEgq+du oGIIL8HlPf79uXwToK0njldTZWNJCAtrnsJzXca6LOgjHxZS2M+yX/XQ08AWRYdS6w8hk9 qs583l5M2y/mDG5aVNHEajerjRbZ+DxAugEc++Tgk75sczTnQn+F33IlNEk4JxCymEDGDF tIjCeF1tg3d32WGLmfPt5QT4+JkhVc92rl5ec8kPNGAWr+xQUus1DC3aXCwatLuKtsrIa6 7/hid13gwDkx55EEe+h7ivu4Y652hVe41oOp72UECgLus0buYjzV8EZOQ6pTRQ== 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 4Pvxnc6wZgzd3n for ; Mon, 10 Apr 2023 05:08:20 +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 33A58KhS040263 for ; Mon, 10 Apr 2023 05:08:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 33A58K3U040262 for bugs@FreeBSD.org; Mon, 10 Apr 2023 05:08:20 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270417] tcpdump does not capture any packets on lagg(4) interface when choosing receive direction Date: Mon, 10 Apr 2023 05:08:21 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable13? mfc-stable12? 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: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270417 --- Comment #3 from commit-hook@FreeBSD.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D11412682562925064591f0abaae63e2a9= ff767e5 commit 11412682562925064591f0abaae63e2a9ff767e5 Author: Zhenlei Huang AuthorDate: 2023-04-02 17:01:51 +0000 Commit: Zhenlei Huang CommitDate: 2023-04-10 05:06:22 +0000 lagg(4): Tap traffic after protocol processing Different lagg protocols have different means and policies to process incoming traffic. For example, for failover protocol, by default received traffi= c is only accepted when they are received through the active port. For lacp proto= col, LACP control messages are tapped off, also traffic will be dropped if they a= re received through the port which is not in collecting state or is not jo= ined to the active aggregator. It confuses if user dump and see inbound traffic= on lagg(4) interfaces but they are actually silently dropped and not passed into the net stack. Tap traffic after protocol processing so that user will have consistent view of the inbound traffic, meanwhile mbuf is set with correct receiving inter= face and bpf(4) will diagnose the right direction of inbound packets. PR: 270417 Reviewed by: melifaro (previous version) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D39225 (cherry picked from commit 5f3d0399e903573e9648385ea6585e54af4d573f) (cherry picked from commit ed44ba413c544c0aa05b3456bc430c816a0e3168) sys/net/if_lagg.c | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) --=20 You are receiving this mail because: You are the assignee for the bug.=