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 18:32:25 +0100 [thread overview]
Message-ID: <1104687145.8894.14.camel@pegasus> (raw)
In-Reply-To: <41A5FC8B00118FAC@resmta05.ono.com> (added by postmaster@resmta05.ono.com)
Hi,
> > Set the device into raw mode. This should stop any processing.
>
> Thanks, this really helped, with de hci device in raw mode now bluez does
> not attend the hci requests, but... how do I transmit hci frames?, simply by
> using send() function with the raw socket? (I'm doing this. I hope the
> frames to be sent to all bt devices in range of my usb dongle).
the HCI is for using the local Bluetooth chip. You can deal with HCI
interfaces of remote chips. You write HCI commands and read HCI event on
the HCI raw socket.
> > Use the hci_vhci driver.
>
> How would be useful the virtual hci driver for this purpose? Did you mean
> that I must set a virtual hci device for receiving and transmitting hci
> traffic?, would it work even if hci_vhci is not attached to a real bt radio?
Look at hciemu. It uses hci_vhci to emulate a Bluetooth device.
> - Will do all game and application traffic (L2CAP and RFCOMM connections are
> used only) go trough the hci traffic I'm forwarding? (I've seen that device
> discovery (COD detection, clock offset....) is not sniffed with the raw
> socket).
Parts of this are LMP or lower. You won't get them.
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
next prev parent reply other threads:[~2005-01-02 17:32 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 [this message]
2005-01-02 19:02 ` radeX
2005-01-02 19:21 ` Marcel Holtmann
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=1104687145.8894.14.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