From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] L2CAP MTU and packet fragmentation?
Date: Mon, 26 Jun 2006 19:21:40 +0200 [thread overview]
Message-ID: <1151342500.7694.40.camel@localhost> (raw)
In-Reply-To: <BED9D15F73EDDE48BF480604236A456001DE40F7@ex1.ad.dcs.gla.ac.uk>
Hi Stephen,
> > If you actually use L2CAP data channel with SOCK_SEQPACKET then you
> > won't see a loss at all. It is a reliable channel.
>
> Yeah, this is what I'm doing, but I'm seeing loss.
>
> I'm following the code from http://people.csail.mit.edu/albert/bluez-intro/x556.html, but not fiddling with anything related to unreliability in section 4.3.2.
>
> Trying the same between two different machines gets me the reliable data transfer.
>
> Am I dealing with bad hardware here? Hardware with bad drivers (I'm dealing with Bluetooth built into a HP iPaq running Familiar Linux, kernel version 2.6.12)? Or an out of date bluez-utils (bluez-utils-nodbus package is version 2.14-r4)?
you can't see loss on the L2CAP data channel. This is impossible.
Regards
Marcel
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 17:21 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
2006-06-26 15:47 ` Marcel Holtmann
2006-06-26 16:48 ` Stephen D. Strowes
2006-06-26 17:21 ` Marcel Holtmann [this message]
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=1151342500.7694.40.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