From: David Woodhouse <dwmw2@infradead.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Diego Liziero <liziero.diego@unimore.it>,
bridge@lists.osdl.org, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-*
Date: Wed, 19 May 2004 18:00:56 +0100 [thread overview]
Message-ID: <1084986055.28151.263.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20040518153608.707e1f81@dell_ss3.pdx.osdl.net>
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 (== 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?
--
dwmw2
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-05-19 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1084467136.3083.27.camel@igno>
[not found] ` <20040513102829.5d5e1484@dell_ss3.pdx.osdl.net>
[not found] ` <1084472140.3354.9.camel@igno>
[not found] ` <20040513111904.6001c62a@dell_ss3.pdx.osdl.net>
2004-05-14 9:27 ` [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-* Diego Liziero
2004-05-17 10:02 ` Diego Liziero
2004-05-18 22:33 ` Stephen Hemminger
2004-05-19 9:34 ` Diego Liziero
2004-05-18 22:36 ` Stephen Hemminger
2004-05-19 17:00 ` David Woodhouse [this message]
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=1084986055.28151.263.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bridge@lists.osdl.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