netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Cong Wang <cwang@twopensource.com>, netdev <netdev@vger.kernel.org>
Subject: Re: how to figure out which device a given IFB is connected to
Date: Mon, 15 Sep 2014 13:55:08 -0700	[thread overview]
Message-ID: <20140915135508.5b346e22@urahara> (raw)
In-Reply-To: <E5E81534-C300-42C1-B2DF-84C006A117AD@gmx.de>

On Mon, 15 Sep 2014 21:06:31 +0200
Sebastian Moeller <moeller0@gmx.de> wrote:

> Hi Mr. Wang,
> 
> Thank you for your help.
> 
> On Sep 15, 2014, at 18:08 , Cong Wang <cwang@twopensource.com> wrote:
> 
> > On Mon, Sep 15, 2014 at 7:37 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> >> I am looking for a way of doing the reverse,i.e.  figuring out for a given IFB if it is “connected” to a real interface and, if yes, which interface. Basically, I want to recycle unused IFBs, but want to make sure that they really are unused…
> >> 
> > 
> > There is no way to figure that out.
> 
> 	That is rather unfortunate, so my only recourse is to get a list of all interfaces and query each whether it is attached to an fib and prune a list of IFBs so that only the unused ones remain (which is far from elegant ;) ).

It can be a many to one mapping.
There are cases where you want multiple incoming devices to all be QoS'd together.

  reply	other threads:[~2014-09-15 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 14:37 how to figure out which device a given IFB is connected to Sebastian Moeller
2014-09-15 16:08 ` Cong Wang
2014-09-15 19:06   ` Sebastian Moeller
2014-09-15 20:55     ` Stephen Hemminger [this message]
2014-09-15 21:24       ` Sebastian Moeller

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=20140915135508.5b346e22@urahara \
    --to=stephen@networkplumber.org \
    --cc=cwang@twopensource.com \
    --cc=moeller0@gmx.de \
    --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).