DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1426] Bonding driver does not receive all packets in 8023ad mode (LACP)
Date: Mon, 29 Apr 2024 18:11:08 +0000	[thread overview]
Message-ID: <bug-1426-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1426

            Bug ID: 1426
           Summary: Bonding driver does not receive all packets in 8023ad
                    mode (LACP)
           Product: DPDK
           Version: 23.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: michel@digirati.com.br
  Target Milestone: ---

The bonding driver does not receive all packets in 8023ad mode (LACP) when it
has two or more members. This bug happens because the bonding driver does not
add the bond's MAC address to the members, so only the member whose MAC address
is the same as the bond receives packets. One can verify the bug by calling
rte_eth_macaddrs_get() on the members after the bond is started.

There are two workarounds:

1. Putting the bond in promiscuous mode with rte_eth_promiscuous_enable(), so
all members receive all packets.

2. Obtaining the MAC address of the bond _after_ adding all members with
rte_eth_macaddr_get(), _and_ adding this MAC address to all members with
rte_eth_dev_mac_addr_add().

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

[-- Attachment #2: Type: text/html, Size: 3161 bytes --]

                 reply	other threads:[~2024-04-29 18:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1426-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).