Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] using scanner with bluez and question to csr-hci-commands
Date: Fri, 24 Jun 2005 17:41:26 +0200	[thread overview]
Message-ID: <1119627686.7129.5.camel@notepaq> (raw)
In-Reply-To: <OF6C4333A9.A9953808-ONC125702A.00447737-C125702A.0049AD28@dcx.dcx>

Hi Andreas,

> A time ago I installed csrsniff and bpasniff from cvs. I have a FTS and a
> BPA-Sniffer.
> 
> When I'm looking now into the cvs I can't find the code again. Why?

the bpasniff is mostly complete. However the master/slave switching are
not really detected and the sniffing of encrypted links is not
supported. The csrsniff is still not finished and maybe never will be.
Ask Frontline for a Linux version of the FTE software.

> Now its time for me to try using this with linux too. currently I am only
> tried the bpasniff. It works.  the outcome from the bpasniff looks like
> baseband packages.
> Have someone written some tools for decoding the packages? Or are there
> some source /info-link available for this topic?

It should decode at least LMP and feed the data into L2CAP. Maybe I have
to check again if I really committed the code. At the moment I am at the
LinuxTag and don't have the BPA-105 with me.

> Second question.
> The csr-ships supporting a lot of additional HCI-commands (I guess its
> implementation specific ...). What I have found in your CVS is the
> possibility to set the BT-Address.
> Is there someone working on getting the following HCI-commands implemented
> in bluez - at least in cvs for testing - too?
> 
> Display supported key length of the module

Use "hciconfig hci0 revision" as root.

> Display acl connection keylength

Use the "bccmd" tool.

> warm-reset Resets the module
> cold-reset Resets the module

Both are not implemented yet.

> Get or set the min keylen
> Get or set the max keylen

You can use the "pskey" tool for it.

> Get or set if a unitkey is used

Don't deal with unit keys at all. It is a security risk.

> It would be helpful for testing BT implementaions, because testing the
> black boxes from our supplier is not so easy without tools.
> Is this genrally possible - or are there some restrictions from CSR?

I can do a lot of special things for CSR chips if you need them. However
you have to ask me nicly or convice me with money or some other gifts ;)

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-06-24 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 13:24 [Bluez-devel] using scanner with bluez and question to csr-hci-commands andreas.knuth
2005-06-24 15:41 ` Marcel Holtmann [this message]
2005-06-26 22:45   ` [Bluez-devel] Function not implemented (38) Nelson Murilo
2005-06-27  5:48     ` Marcel Holtmann
2005-06-27 17:54       ` Nelson Murilo
2005-06-27 18:20         ` 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=1119627686.7129.5.camel@notepaq \
    --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