netdev - Fw: [Bug 214631] New: Creating a macvlan with as bridge as parent -> NO-CARRIER on both

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20211006081953.539005df@hermes.local>
Date:   Wed, 6 Oct 2021 08:19:53 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 214631] New: Creating a macvlan with as bridge as parent
 -> NO-CARRIER on both



Begin forwarded message:

Date: Wed, 06 Oct 2021 15:09:30 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.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@...workplumber.org
          Reporter: jan@...andtsheer.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.