All of lore.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: Thu, 10 Feb 2005 15:47:57 +0100	[thread overview]
Message-ID: <1108046877.15974.57.camel@pegasus> (raw)
In-Reply-To: <42005A510007CC0F@resmta05.ono.com> (added by postmaster@resmta05.ono.com)

Hi,

> As you remember I was developing a gateway for tunneling the hci traffic
> over TCP and be able to transfer files and play bluetooth games at long
> distances.
> I wrote a simple and very rudimentary C++ test program but didn't work. I
> think the problem is the destination bluetooth address, would I need to
> parse
> the hci frames to set the bt address to its correct value?, I don't know
> how to do this, I am really lost.
> I tested the program with another friend running the same program with two
> nokia n-gage.
> 
> If you can help me here is the source code, please feel free to modify
> whatever
> you want and tell me how can I solve this problem or give me a new way of
> doing this.
> (I marked up the important part of the main loop so you can see the main
> idea witouth reading the full source), at the end is the program and hcidump
> output.
> 
> If you want the full source (all files and makefile) tell me.

using C++ is actually too much for such a project, because OO is useless
in this case and personally I don't like C++ and so I won't comment on
your code.

If you wanna do HCI forwarding then you must first use the HCI device in
raw mode and even then I don't think that this going to work. You must
map a lot of commands to events and vice versa. For example a connect
request from on side must result in a create connection on the other
side and then you must do the HCI flow control right.

And yes, you must do a BD_ADDR and also connection handle translation
for every command/event exchange. I am not sure if this will ever work,
but even if, it is a lot of work and you need a deep understanding of
the HCI.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-02-10 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 12:19 [Bluez-devel] Several bluetooth dongles at time schnelte
2005-02-10 12:41 ` Marcel Holtmann
2005-02-10 13:10   ` [Bluez-devel] HCI Forwarding radeX
2005-02-10 14:47     ` Marcel Holtmann [this message]
2005-02-11 18:51   ` [Bluez-devel] Several bluetooth dongles at time Matthias Schnelte
2005-02-11 19:03     ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
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
2005-01-02 20:26           ` radeX
2005-01-02 20:45             ` 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=1108046877.15974.57.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 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.