From: "Kishore A K" <kishoreak@myw.ltindia.com>
To: <dwmw2@infradead.org>, <shemminger@osdl.org>
Cc: <bridge@lists.osdl.org>, <bluez-devel@lists.sourceforge.net>,
<liziero.diego@unimore.it>
Subject: Re: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep deviceswith kernel 2.6.6-*
Date: Fri, 21 May 2004 11:49:33 +0530 [thread overview]
Message-ID: <s0adece8.044@EMAIL> (raw)
The ifreq structure to br_dev_do_ioctl() gives you the interface index
(rq->ifr_ifindex) which is currently not being used.
May be it can help..
-Kishore
>>> David Woodhouse <dwmw2@infradead.org> 05/19/04 10:30PM >>>
On Tue, 2004-05-18 at 15:36 -0700, Stephen Hemminger wrote:
> Hmm, since all the blue tooth devices have the same address.
> Deleting the first one will cause the entry in the forwarding table
> to be deleted, that might cause your problem. Perhaps we need a
> reference count on the number of interfaces with the same address =
(yuck).
That seems like a reasonable answer. I believe there's also some
workstation hardware with multiple Ethernet devices, all sharing the
same MAC address (=3D=3D hostid). It's not just Bluetooth. How does this
work with VLAN bridging?
Precisely what is it that's indexed on the interface's MAC address,
rather than the (index of the) physical interface itself?
--=20
dwmw2
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2004-05-21 6:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=s0adece8.044@EMAIL \
--to=kishoreak@myw.ltindia.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bridge@lists.osdl.org \
--cc=dwmw2@infradead.org \
--cc=liziero.diego@unimore.it \
--cc=shemminger@osdl.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