All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Fontaine <arnau@milkypond.org>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridge interface always down since Linux >= 2.6.39
Date: Thu, 30 Jun 2011 15:05:36 +0200	[thread overview]
Message-ID: <878vsjqxjz.fsf@duckcorp.org> (raw)

Hello,

After upgrading my  kernel to 2.6.39 (I also  tested with 3.0.0-rc4), my
bridge interface  with only TAP interfaces  is always down  (the flag is
NO_CARRIER and  operational state is  DOWN) despite it was  working well
with  previous  versions of  the  kernel  (the  state was  LOWER_UP  and
operational state  was UNKNOWN). Before, running  the following commands
was enough to activate the bridge interface:

  1. brctl addbr br0
  2. ip link set br0 up

Only by attaching a real network interface (such as eth0) to the bridge,
it finally works well  but I would like to be able  to not only use real
network interfaces.

Any idea? Many thanks in advance.

Regards,
-- 
Arnaud Fontaine

             reply	other threads:[~2011-06-30 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 13:05 Arnaud Fontaine [this message]
2011-06-30 16:22 ` [Bridge] Bridge interface always down since Linux >= 2.6.39 Stephen Hemminger
2011-06-30 19:58   ` Arnaud Fontaine

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=878vsjqxjz.fsf@duckcorp.org \
    --to=arnau@milkypond.org \
    --cc=bridge@lists.linux-foundation.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 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.