netdev - how to figure out which device a given IFB is connected to

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-next>] [day] [month] [year] [list]

Message-Id: <CBDE840F-96BA-4839-9774-86F72E99E964@gmx.de>
Date:	Mon, 15 Sep 2014 16:37:30 +0200
From:	Sebastian Moeller <moeller0@....de>
To:	netdev@...r.kernel.org
Subject: how to figure out which device a given IFB is connected to

Hi All,

I hope I am directing this to the correct mailing list, otherwise please excuse the distraction… 

I am trying to figure out a way to semi-automatically manage a set of IFB devices for a number of network interfaces. Currently I have no problem finding out if a given “real” interfaces is connected to an IFB:

root@...ktmulle:~# tc -s filter show parent ffff: dev ge00
filter protocol all pref 10 u32 
filter protocol all pref 10 u32 fh 800: ht divisor 1 
filter protocol all pref 10 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:1 
  match 00000000/00000000 at 0
	action order 1: mirred (Egress Redirect to device ifb1) stolen
 	index 47 ref 1 bind 1 installed 521 sec used 3 sec

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…

Thanks in advance
	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