All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 15 Nov 2006 14:47:13 +0100	[thread overview]
Message-ID: <1163598433.4678.0.camel@localhost> (raw)
In-Reply-To: <455B1164.5050607@kernelconcepts.de>

Hi Nils,

> The issue was that some Bluetooth dongles do not contain a valid
> Bluetooth MAC address. Well, this is against the spec and so the dongles
> are bad but sometimes users cannot avoid to get such. So I still see the
> need that we do as good as we can to help those users and get those bad
> dongles working.
> 
> Long story short, Marcel's bdaddr application contained in the latest
> release of bluez-utils works, at least for the two dongles I have with
> ISS chipsets. So the BDADDR can be set now.
> 
> I wanted an automatic solution so that when I plug the dongle in it is
> automatically assigned "an" address. So first I created an udev rule
> that calls an application when the specific USB device with the
> vendorid:deviceid I know to be bad is inserted - in my case 1131:1001
> (plaease let me know more!).
> 
> 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.

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

  reply	other threads:[~2006-11-15 13:47 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 [this message]
2006-11-15 14:50                   ` Nils Faerber
2006-11-15 15:05                   ` Stefan Seyfried
2006-11-16 10:35                     ` Marcel Holtmann

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=1163598433.4678.0.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.