public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] HCI forwarding
Date: Sun, 02 Jan 2005 20:21:01 +0100	[thread overview]
Message-ID: <1104693661.8894.25.camel@pegasus> (raw)
In-Reply-To: <41A7074C0036241B@resmta03.ono.com> (added by postmaster@resmta03.ono.com)

Hi,

> Device detection is not a problem since bluez does it for me (I only have to
> set the local class of device to the correct value (0x500204) in order to
> deceiving mobile phones in both sides). I conform with forwarding L2CAP and
> RFCOMM profile connection data, SDP and the rest of necessary HCI commands
> and events to make possible a long-distance L2CAP / RFCOMM session.

forwarding L2CAP channels or also ACL data packets is very easy. However
the ACL MTU should match. The role switches might be a little tricky.
Forwarding the HCI commands and events is not that easy. You must keep
an eye on the flow control mechanism of HCI, but this is all still
doable and there are more ways for doing it.

> Is this possible in this way?, In other?, Am I wrong?
> (I wrote the app sniffing and forwarding hci frames (it seems that "works")
> but I had no chance for testing it).

It is possible and the best way depends on what you wanna do. Basically
I used L2CAP and RFCOMM forwarding a lot of this to crack protocol stuff
that was going on between some devices. Best example is the Nokia PhoNet
protocol.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-01-02 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02  4:29 [Bluez-devel] HCI forwarding radeX
2005-01-02 11:39 ` Marcel Holtmann
2005-01-02 16:58   ` radeX
2005-01-02 17:32     ` Marcel Holtmann
2005-01-02 19:02       ` radeX
2005-01-02 19:21         ` Marcel Holtmann [this message]
2005-01-02 20:26           ` radeX
2005-01-02 20:45             ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-02-10 12:41 [Bluez-devel] Several bluetooth dongles at time Marcel Holtmann
2005-02-10 13:10 ` [Bluez-devel] HCI Forwarding radeX
2005-02-10 14:47   ` 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=1104693661.8894.25.camel@pegasus \
    --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