From: Marcel Holtmann <marcel@holtmann.org>
To: Moritz Gmelin <moritz.gmelin@avetana.de>
Cc: Till Harbaum <harbaum@beecon.de>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Zero length L2CAP packets
Date: Tue, 22 Feb 2005 01:17:08 +0100 [thread overview]
Message-ID: <1109031428.7626.84.camel@pegasus> (raw)
In-Reply-To: <2def10fdd2a185bcddd4562929cd1417@avetana.de>
Hi Moritz,
> I just tried writing a 0-length packet on my open L2CAP Connection and
> I cannot see anything happening with hcidump. The remote end is a Mac.
> But I guess that I should see anything regardless of the remote end.
> 1-byte packets and more get transferred correctly but
>
> write (fd, "foo", 0);
>
> on my open L2CAP Descriptor fd does not give any reaction in hcidump.
>
> my version of bluez is libbluetooth1 2.11-1
update the library and utils and also the kernel. Maybe you need to use
send() for sending 0 byte payload, because this is what is used in the
l2test program.
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
prev parent reply other threads:[~2005-02-22 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 10:12 [Bluez-devel] Zero length L2CAP packets Till Harbaum
2005-02-10 14:04 ` Marcel Holtmann
[not found] ` <2def10fdd2a185bcddd4562929cd1417@avetana.de>
2005-02-22 0:17 ` 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=1109031428.7626.84.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=harbaum@beecon.de \
--cc=moritz.gmelin@avetana.de \
/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