From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] connectionless L2CAP
Date: Wed, 21 Dec 2005 14:56:13 +0100 [thread overview]
Message-ID: <1135173373.14627.0.camel@localhost> (raw)
In-Reply-To: <43A95B0B.2040909@in.tum.de>
Hi Aleksandar,
> I'm actually trying to send a data packet between 2 bluetooth devices
> over 100 meters. I haven't went really deep into the bluetooth specs,
> but I assume that because of the long range a connection might not be
> possible, so that's why I just want to broadcast some packets and hope
> that some will arrive at the other end. Is this possible ?
what's the problem with 100 meters range. Use a pair of class 1 dongles
and you are fine.
> Btw./l2test with 00:00:00:00:00:00 fails too, but the bluetooth baseband
> specification section 3.3 says that "ACL packets not addressed to a
> specific slave are considered as broadcast packets and are read by every
> slave". I have 1 device in range (I can see it with hcitool scan, l2test
> succeeds with that device).
You still need the piconet. No piconet no data transfer over the air.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-12-21 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 12:32 [Bluez-users] connectionless L2CAP Aleksandar Kanchev
2005-12-21 12:45 ` Marcel Holtmann
2005-12-21 13:39 ` Aleksandar Kanchev
2005-12-21 13:56 ` Marcel Holtmann [this message]
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=1135173373.14627.0.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).