From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] New HCI-USB device, no MAC?
Date: Thu, 16 Nov 2006 11:35:58 +0100 [thread overview]
Message-ID: <1163673358.5169.31.camel@localhost> (raw)
In-Reply-To: <20061115150540.GB16156@suse.de>
Hi Stefan,
> > > Then I created a small shell script which sets a "more correct" address
> > > than the default 11:11:11:11:11:11. I assume in this script that an
> > > ethernet device is present in the system as eth0 and use its MAC for the
> > > Bluetooth dongle too.
> > >
> > > I did this for two reasons:
> > > 1. On the same machine I always want to have the same BDADDR, so random
> > > was no choice.
> > > 2. The ethernet addresses also have to follow the same rules as
> > > Bluetooth MAC addresses, i.e. they have to be unique. So the probability
> > > of a collision is very low.
> >
> > and now PAN will stop working, because the eth0 and bnep0 will have the
> > same MAC address. Not a good idea.
>
> Well, after reading http://en.wikipedia.org/wiki/MAC_address i guess that
> we just could set bit 1 of the 6th byte to signal "locally administered"
> _and_ distinguish that address from the ethernet MAC address.
>
> Or is this totally wrong?
>
> But then, what happens if you plug two of those adapters into one machine?
the problem is that this address suppose to be unique and these guys
screwed it up. Period. Whatever you try to solve this will have its
downside somewhere. However using the hostid and actually storing the
value for later use after reboot could maybe a valid solution.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-11-16 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 10:52 [Bluez-devel] New HCI-USB device, no MAC? Nils Faerber
2006-03-09 13:51 ` Marcel Holtmann
2006-03-09 15:46 ` Nils Faerber
2006-03-09 16:56 ` Marcel Holtmann
2006-04-12 20:00 ` [Bluez-devel] " Evan Paul Fletcher
2006-04-12 20:09 ` Marcel Holtmann
2006-04-13 6:02 ` Sowmya Gattupalli
2006-04-13 6:30 ` Mayank Batra
2006-04-24 10:54 ` Nils Faerber
2006-04-24 11:04 ` Marcel Holtmann
2006-04-28 10:54 ` Nils Faerber
2006-11-15 13:08 ` [Bluez-devel] " Nils Faerber
2006-11-15 13:47 ` Marcel Holtmann
2006-11-15 14:50 ` Nils Faerber
2006-11-15 15:05 ` Stefan Seyfried
2006-11-16 10:35 ` Marcel Holtmann [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=1163673358.5169.31.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).