From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@nvidia.com>, razor@blackwall.org
Cc: bridge@lists.linux.dev
Subject: Fw: [Bug 198297] Unable to add ethX to bridge if ethX.<VLAN_ID> is already present in this bridge
Date: Wed, 16 Oct 2024 08:19:36 -0700 [thread overview]
Message-ID: <20241016081936.736e0db7@hermes.local> (raw)
Kernel bugzilla new report forwarding to bridge maintainers
Begin forwarded message:
Date: Wed, 16 Oct 2024 06:44:35 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198297] Unable to add ethX to bridge if ethX.<VLAN_ID> is already present in this bridge
https://bugzilla.kernel.org/show_bug.cgi?id=198297
AntonioBDaniels (annawhuggins@hotmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |annawhuggins@hotmail.com
--- Comment #5 from AntonioBDaniels (annawhuggins@hotmail.com) ---
The bug report on Kernel.org is an issue where adding a physical Ethernet
interface (ethX) to a bridge will fail if a VLAN interface (ethX.<VLAN_ID>) is
already present on that bridge. This issue poses a challenge for users trying
to configure a network
http://www.ralinktech.com/ralink/Home/Backing/Linux.html
https://geometrydash-scratch.com bridge with a VLAN because it conflicts with
the intended network
--
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:[~2024-10-16 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=20241016081936.736e0db7@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux.dev \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.