lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <719B90A7-0D8A-4CBB-A0EB-2BDCAA36FEEC@gmx.de>
Date:	Mon, 15 Sep 2014 23:24:54 +0200
From:	Sebastian Moeller <moeller0@....de>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	Cong Wang <cwang@...pensource.com>, netdev <netdev@...r.kernel.org>
Subject: Re: how to figure out which device a given IFB is connected to

Hello Mr. Hemminger,


On Sep 15, 2014, at 22:55 , Stephen Hemminger <stephen@...workplumber.org> wrote:

> On Mon, 15 Sep 2014 21:06:31 +0200
> Sebastian Moeller <moeller0@....de> wrote:
> 
>> Hi Mr. Wang,
>> 
>> Thank you for your help.
>> 
>> On Sep 15, 2014, at 18:08 , Cong Wang <cwang@...pensource.com> wrote:
>> 
>>> On Mon, Sep 15, 2014 at 7:37 AM, Sebastian Moeller <moeller0@....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.

	Good to know, thanks for this information.

Best Regards
	Sebastian Moeller


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ