public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] UDP and TCP packets across Bluez connections?
Date: Sat, 22 Sep 2007 09:46:21 +0200	[thread overview]
Message-ID: <1190447181.5133.50.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <OFFBAD6020.4E382E4A-ON8825735D.005AD683-8825735D.005D2673@etas.de>

Hi,

> I have an emebdded Linux app that currently listens on a socket that
> receives messages from multiple interfaces (e.g. ethernet, USB with
> RNDIS, wireless). I want to add Bluetooth support. 
> 
> My question: Do Bluez interfaces to Bluetooth devices act like any
> other IP interface? 
> 
> I found example source code on the internet of sockets being opened
> with AF_BLUETOOTH as the socket domain (i.e. the first argument to the
> socket call). Does one have to always do it that way in order to
> receive inbound messages on a Bluetooth interface? 
> 
> I came across text that makes it sound like one uses L2CAP in place of
> UDP and RFCOMM in place of TCP. 
> http://people.csail.mit.edu/albert/bluez-intro/x95.html 
> 
> http://bluez.sourceforge.net/contrib/HOWTO-PAN 
> 
> So then is it not possible to do TCP/IP across Bluetooth connections?
> Does one need to write application level code that is different for
> Bluetooth as compared to ethernet/USB/wireless? 

so first of all. The socket interface doesn't mean IP. It is a generic
way of using network protocols. And network protocols doesn't mean IP
only. There are more network protocols than you can think of.

> Also, if one can do TCP/IP over Bluetooth from Linux then does Windows
> recognize incoming TCP and UDP packets without loading a special
> driver on Windows? Currently with USB one uses RNDIS on Windows and an
> RNDIS equivalent driver configuration on Linux. Then Windows and Linux
> can talk. But to do TCP/IP between Linux and Windows over Bluetooth
> what does one do? 
> 
> Or if there is not real TCP/IP support with Bluetooth does Windows
> understand RFCOMM and L2CAP? 

If you wanna have TCP then you can do Ethernet over Bluetooth which is
done by PAN over BNEP. And that would interact with Windows or any other
OS for that matter.

> Also, is there some sort of authoritative write-up on a web page
> somewhere about TCP/IP on Bluetooth? I've Googled up read probably 100
> web pages looking for better info and haven't found it.

The first thing that you should read is a Bluetooth introduction that
explains the various protocol layers that can be used for various tasks.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-09-22  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 16:57 [Bluez-users] UDP and TCP packets across Bluez connections? rparker
2007-09-22  7:46 ` Marcel Holtmann [this message]
2007-09-22 12:47   ` Timothy Murphy
2007-09-22 18:53     ` Marcel Holtmann
2007-09-24 23:49   ` rparker

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=1190447181.5133.50.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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