From: Dan Williams <dcbw@redhat.com>
To: netdev@vger.kernel.org
Subject: bridge interface initial carrier state
Date: Mon, 11 Feb 2013 14:01:55 -0600 [thread overview]
Message-ID: <1360612915.8633.6.camel@dcbw.foobar.com> (raw)
Hi,
I'm wondering if the initial carrier state of 'on' is intentional for a
bridge without ports; immediately after adding ports, the carrier is
recalculated and depends on the combined state of each port's carrier
and STP forwarding state. So a userspace program attempting to decide
whether the bridge was usable or not has to look at both (a) how many
ports are available and (b) bridge carrier state, instead of just
looking at the bridge carrier state.
Dan
next reply other threads:[~2013-02-11 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 20:01 Dan Williams [this message]
2013-02-11 21:58 ` bridge interface initial carrier state Stephen Hemminger
2013-02-12 21:06 ` Jiri Pirko
2013-02-12 21:10 ` David Miller
2013-02-11 21:59 ` Stephen Hemminger
2013-02-11 22:46 ` Dan Williams
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=1360612915.8633.6.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--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).