From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] l2cap retransmission
Date: Fri, 17 Dec 2004 15:26:54 +0100 [thread overview]
Message-ID: <1103293614.28046.99.camel@pegasus> (raw)
In-Reply-To: <2de4657604121705486b925ee0@mail.gmail.com>
Hi Manjunath,
> in l2test suppose a data mismatch or error occurs, are the packets
> retransmitted???? if yes, can we watch the packet retransmission in
> hcidump......
use the source, Luke ;)
The L2CAP layer is reliable and so there can't be an error. But if there
is a retransmission you will see it with hcidump.
> i have been able to see some data and sequence mismatch packets and
> the connection was not brought down....so i assume that retransmission
> must have taken place.....
You know that l2test is a test program, do you?
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-12-17 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 13:48 [Bluez-users] l2cap retransmission Manjunath Prabhu
2004-12-17 14:18 ` [Bluez-users] passive inquiry Paolino paperino
2004-12-17 14:24 ` Marcel Holtmann
2004-12-17 14:30 ` Peter Stephenson
2004-12-17 14:34 ` Fred Schaettgen
2004-12-17 14:53 ` Steven Singer
2005-03-02 13:57 ` Paolino paperino
2005-03-02 16:21 ` Stephen Crane
2004-12-17 14:26 ` 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=1103293614.28046.99.camel@pegasus \
--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