[Bug 270417] tcpdump does not capture any packets on lagg(4) interface when choosing receive direction

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 10 Apr 2023 05:08:21 UTC

--- Comment #3 from commit-hook@FreeBSD.org ---
A commit in branch stable/12 references this bug:


commit 11412682562925064591f0abaae63e2a9ff767e5
Author:     Zhenlei Huang <zlei@FreeBSD.org>
AuthorDate: 2023-04-02 17:01:51 +0000
Commit:     Zhenlei Huang <zlei@FreeBSD.org>
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
    traffic. For example, for failover protocol, by default received traffic is
    accepted when they are received through the active port. For lacp protocol,
    control messages are tapped off, also traffic will be dropped if they are
    received through the port which is not in collecting state or is not joined
    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
    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 interface
    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(-)

You are receiving this mail because:
You are the assignee for the bug.