From: Stephen Strowes <sds@dcs.gla.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] L2CAP MTU and packet fragmentation?
Date: Fri, 23 Jun 2006 13:36:45 +0100 [thread overview]
Message-ID: <1151066205.6247.19.camel@addu> (raw)
Hi,
Forgive me if this has been answered time and again, but I can't seem to
access the archives just now. Google's not helping me much either.
I have a bit of BlueZ code, which I have to make use of L2CAP sockets to
communicate between devices. I've seen that I can alter the MTU for
packets, but I'm surprised that packets don't get fragmented as per
plain UDP when a packet larger than the MTU is passed to send().
Have I missed a configuration option somewhere?
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.
Cheers,
Stephen.
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 reply other threads:[~2006-06-23 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 12:36 Stephen Strowes [this message]
2006-06-26 12:17 ` [Bluez-users] L2CAP MTU and packet fragmentation? Marcel Holtmann
2006-06-26 15:03 ` Stephen Strowes
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=1151066205.6247.19.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