From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <005601c63854$a2fdace0$0f01a8c0@tungemaskin> From: =?UTF-8?Q?J=C3=B8rgen_Hovland?= References: <01f701c63728$6203bef0$4a27b3d5@tungemaskin><20060221141743.32d66879@localhost.localdomain><003101c6378b$f5f65060$4a27b3d5@tungemaskin> <20060222080250.363d5e30@localhost.localdomain> Subject: Re: [Bridge] physical interface on a bridge Date: Thu, 23 Feb 2006 09:39:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original" Content-Transfer-Encoding: 8bit List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephen Hemminger Cc: bridge@lists.osdl.org (sorry about the empty last email) ----- Original Message ----- From: "Stephen Hemminger" > On Wed, 22 Feb 2006 09:42:49 +0100 > Jørgen Hovland wrote: > >> So there is no way to get the physical interface from a mac address? > > You can read the forwarding database (see brctl sources for how). > But the value can change as result of traffic. > I did actually look at the code before I emailed the list. Sorry if I am missing something, but a fdb_entry maps a hardware address to a port number. This arbitary port number points to the port_info structure which seems to only hold information about what bridge it belongs to. And the bridge_info structure doesn't contain any information either. The only place I can find something that might be useful is in linux/netdevice.h and the "struct net_bridge_port *br_port" under the net_device structure. This is inside the kernel as it needs __KERNEL__ defined in order to use it, or is this what I am looking for? Thank you once again Joergen