From: Stephen Strowes <sds@dcs.gla.ac.uk>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2CAP MTU and packet fragmentation?
Date: Mon, 26 Jun 2006 16:03:12 +0100 [thread overview]
Message-ID: <1151334192.29221.7.camel@addu> (raw)
In-Reply-To: <1151324247.7694.10.camel@localhost>
Hi,
On Mon, 2006-06-26 at 14:17 +0200, Marcel Holtmann wrote:
> > I could live with the MTU being 64k with no fragmentation, but I seem to
> > get quite a lot of corrupt packets over around 2kB.
>
> I have no idea what you are talking about. The L2CAP layer is reliable
> and the underlaying ACL link, too.
Sorry, correction, I get a lot of lost packets. I assume either because
they've become corrupted, or perhaps because they never arrive.
I get between 20-40% packet loss with packet sizes around 3000 bytes,
and more loss as packet sizes increase. l2ping says 56% loss at 3500
bytes.
This loss is what prompted my question. This behaviour, actually, is why
I'm using L2CAP -- because it was likened to UDP in what I'd read
previously. Ironically, perhaps, it's just a little *too* lossy :-)
I'll either bolt on some packet segmentation to my app, or use RFCOMM
for now.
Cheers,
S.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-06-26 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 12:36 [Bluez-users] L2CAP MTU and packet fragmentation? Stephen Strowes
2006-06-26 12:17 ` Marcel Holtmann
2006-06-26 15:03 ` Stephen Strowes [this message]
2006-06-26 15:47 ` Marcel Holtmann
2006-06-26 16:48 ` Stephen D. Strowes
2006-06-26 17:21 ` Marcel Holtmann
2006-06-26 17:39 ` Stephen D. Strowes
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=1151334192.29221.7.camel@addu \
--to=sds@dcs.gla.ac.uk \
--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).