* [Bluez-devel] Zero length L2CAP packets
@ 2005-02-10 10:12 Till Harbaum
2005-02-10 14:04 ` Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: Till Harbaum @ 2005-02-10 10:12 UTC (permalink / raw)
To: BlueZ Mailing List; +Cc: Moritz Gmelin
Hi,
while working on the avetana jsr82 implementation we discovered, that the bt
spec as well as jsr82 allow to transmit zero length l2cap packets. IMHO the
linux socket interface does not support zero length packets and a read
returning zero indicates an end of file (in this case meaning that the
connection has been closed).
What happens if the other side actually sends a zero length packet? Is this
dropped inside the kernel? Or will read return zero which i'll misinterpret
as the eof marker? How can i distinguish between eof and a zero length
packet?
Regards,
Till
--
Dr.-Ing. Till Harbaum Tel.: +49 721 4998963
BeeCon GmbH Fax: +49 721 4998962
Haid-und-Neu Strasse 7, 76131 Karlsruhe Mobil: +49 179 9087904
harbaum@beecon.de http://www.beecon.de
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] Zero length L2CAP packets
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>
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2005-02-10 14:04 UTC (permalink / raw)
To: BlueZ Mailing List; +Cc: Moritz Gmelin
Hi Till,
> while working on the avetana jsr82 implementation we discovered, that the bt
> spec as well as jsr82 allow to transmit zero length l2cap packets. IMHO the
> linux socket interface does not support zero length packets and a read
> returning zero indicates an end of file (in this case meaning that the
> connection has been closed).
>
> What happens if the other side actually sends a zero length packet? Is this
> dropped inside the kernel? Or will read return zero which i'll misinterpret
> as the eof marker? How can i distinguish between eof and a zero length
> packet?
actually I see no problem with zero length L2CAP packets. I modified the
l2test program to actually be able to send and receive them, but there
is no problem at all. This is a socket and not a file and so you might
use poll() or select() to detect the hangup of the connection and not
some weird zero length magic.
The kernel btw is dropping no packets. I see all of these zero packets
flying from one end to the other.
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-02-22 0:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox