All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Fontaine <arnau@milkypond.org>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge interface always down since Linux >= 2.6.39
Date: Thu, 30 Jun 2011 21:58:31 +0200	[thread overview]
Message-ID: <87k4c38520.fsf@duckcorp.org> (raw)
In-Reply-To: <20110630092258.7c1119a3@nehalam.ftrdhcpuser.net>    (Stephen Hemminger's message of "Thu, 30 Jun 2011 09:22:58 -0700")

Hi,

> There are  two flags, IFF_UP  - admin up/down and  IFF_RUNNING carrier
> up/down The IFF_UP is controlled manually, and IFF_RUNNING is what you
> are talking about.

Interesting, thank you very much for the explanation.

> In older  kernel versions, the  bridge device always  asserted carrier
> even if all  ports did not have carrier. Now it  reflects the state of
> the  underlying device.  In  your case  the  problem is  that the  tap
> interfaces aren't reporting carrier.

This  is what  I understood  by testing  with a  real  network interface
attached to the  bridge, however I was not sure  whether it was intended
or a regression.  In this  particular case, a tap interface is reporting
carrier when  an userspace program is  attached to it AFAIK,  so I guess
there  is  nothing else  I  can do  besides  of  attaching an  userspace
program, right?

Thanks for the quick response.

Cheers,
-- 
Arnaud Fontaine

      reply	other threads:[~2011-06-30 19:58 UTC|newest]

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

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=87k4c38520.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.