From: Diego Liziero <liziero.diego@unimore.it>
To: Paolino paperino <vonzoltan@yahoo.it>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: [Bluez-users] problems with bytestream
Date: Wed, 13 Oct 2004 15:46:20 +0200 [thread overview]
Message-ID: <1097675179.1075.40.camel@igno> (raw)
In-Reply-To: <20041012162957.12307.qmail@web40614.mail.yahoo.com>
Hi Andrea,
I took a look at l2test.c and I saw that
at the beginning of each packet sent
there is a small header.
The first 32 bits are used for the sequence number
and the following 16 for the packet size.
l2test[3491]: Recevied 18 bytes
00000000: 01 00 00 00 12 00 7f 7f 7f 7f 7f 7f 7f 7f 7f 7f
.........|seq-number | len | payload
.........| (little endian) |
However I tested it with smaller packet sizes and it seems
to work here flawlessly.
l2test -s -b 1 -N 1 XX:XX:XX:XX:XX:XX
l2test -d
l2test[3488]: Connect from XX:XX:XX:XX:XX:XX [imtu 672, omtu 672,
flush_to 65535]
l2test[3488]: Receiving ...
l2test[3488]: Recevied 1 bytes
00000000: 00 .
l2test[3488]: Disconnect. Success
I used csr based USB dongles with latest bluez libs & utils.
Ciao,
Diego Liziero.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-13 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 16:29 [Bluez-users] problems with bytestream Paolino paperino
2004-10-13 13:46 ` Diego Liziero [this message]
2004-10-13 14:38 ` [Bluez-devel] Re: [Bluez-users] problems with bytestream + rfcomm socket problems Paolino paperino
2004-10-14 8:26 ` Diego Liziero
2004-10-20 13:49 ` Paolino paperino
2004-10-20 13:49 ` Paolino paperino
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=1097675179.1075.40.camel@igno \
--to=liziero.diego@unimore.it \
--cc=bluez-devel@lists.sourceforge.net \
--cc=diego.liziero@unimore.it \
--cc=vonzoltan@yahoo.it \
/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