From: Diego Liziero <liziero.diego@unimore.it>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org, bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-*
Date: Fri, 14 May 2004 11:27:25 +0200 [thread overview]
Message-ID: <1084526845.6774.55.camel@igno> (raw)
In-Reply-To: <20040513111904.6001c62a@dell_ss3.pdx.osdl.net>
On Thu, 2004-05-13 at 20:19, Stephen Hemminger wrote:
> I do think each bluetooth device should have a different hardware
> address to keep themselves sane.
Things are not so easy.
Each bluetooth dongle has it's own harware address (MAC)
and in a piconet (one master and up to 7 slaves)
at each PAN connection a device called bnep0, ... bnep6
is created on the master PC by bluez with the same MAC of the dongle.
Each device bnep? for each maste-slave point to point connection.
And the bad thing is that when one of these connection is
closed, its relative device (bnep?) cease to exist.
And this create serious problems with things like
a dhcp server and a bridge.
Regards,
Diego
-------------------------------------------------------
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
next parent reply other threads:[~2004-05-14 9:27 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 ` Diego Liziero [this message]
2004-05-17 10:02 ` [Bluez-devel] Re: [Bridge] bridging bluetooth bnep devices with kernel 2.6.6-* 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
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=1084526845.6774.55.camel@igno \
--to=liziero.diego@unimore.it \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bridge@lists.osdl.org \
--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