From: "Uichin (Eugene) Lee" <netssenger@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] data fragment
Date: Sat, 2 Dec 2006 03:40:21 -0800 [thread overview]
Message-ID: <d66c3bdf0612020340r4b44e500i1a6c6ad6917875b7@mail.gmail.com> (raw)
Hi All,
I have an urgent question. I'm sending a 2300B packet from one machine
to another machine through L2CAP. I used hcidump to see the
fragmentation in L2CAP.
I looked at the kernel code, and realized that L2CAP uses "ACL_MTU" to
do the fragmentation. hcidump at the sender side shows that
< ACL data: handle 1 flags 0x01 dlen: 120
However, hcidump at the receiver side shows like this:
> ACL data: handle 42 flags 0x01 dlen: 224
=> 10 times +
> ACL data: handle 42 flags 0x01 dlen: 64
Total 2304 (2300B payload + 4 bytes - CID/Length)
What's happening here? At the lower layer (i.e., LMP), pack those
packets and then create another ACL packet with length 224 (the size
of DM5 packet). It seems like LMP packs uppper level data packets
into current baseband packet format. Is that true?
Thank you.
--
Uichin (Eugene) Lee
Ph.D. Student UCLA CS Dept.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-12-02 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 11:40 Uichin (Eugene) Lee [this message]
2006-12-03 13:31 ` [Bluez-users] data fragment Marcel Holtmann
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=d66c3bdf0612020340r4b44e500i1a6c6ad6917875b7@mail.gmail.com \
--to=netssenger@gmail.com \
--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