From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 214631] New: Creating a macvlan with as bridge as parent -> NO-CARRIER on both
Date: Wed, 6 Oct 2021 08:19:53 -0700 [thread overview]
Message-ID: <20211006081953.539005df@hermes.local> (raw)
Begin forwarded message:
Date: Wed, 06 Oct 2021 15:09:30 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 214631] New: Creating a macvlan with as bridge as parent -> NO-CARRIER on both
https://bugzilla.kernel.org/show_bug.cgi?id=214631
Bug ID: 214631
Summary: Creating a macvlan with as bridge as parent ->
NO-CARRIER on both
Product: Networking
Version: 2.5
Kernel Version: 5.7+
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: jan@delandtsheer.eu
Regression: No
When creating a macvlan with a bridge as parent, interfaces brought up, have
NO-CARRIER.
Only when connecting another type of interface to the bridge (like a dummy) and
bring it up, the bridge and macvlan start forwarding
ip netns add tns
ip link add tbr type bridge
ip link add tmv link tbr type macvlan mode bridge
ip link set tmv netns tns
ip link set tbr up
ip -n tns link set lo up
ip -n tns link set tmv up
behaviour :
kernel 5.4 -> that always works
kernel 5.10 -> mostly works, __sometimes__ not
kernel 5.14 -> never works
verifyable with `ip link show dev tbr` having NO-CARRIER
When it doesn't work:
ip link add tdum type dummy
ip link set tdum master tbr
ip link set tdum up
and then the bridge and macvlans start forwarding
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-06 15:19 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=20211006081953.539005df@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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).