public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolino paperino <vonzoltan@yahoo.it>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] rfcomm sockets problems
Date: Wed, 13 Oct 2004 15:38:44 +0200 (CEST)	[thread overview]
Message-ID: <20041013133844.49389.qmail@web40627.mail.yahoo.com> (raw)
In-Reply-To: <200410131143.26811.n1c0l4s.l3@wanadoo.fr>

Hi,
I've used the test program rctest to test the
capability of open a connection between two linux
boxes with bt. Well the protocol seems (l2test) to be
instable, when i transmit  a sequence of packets
composed of only 1 bytes, the reader loose some
packets. The command lines i use are:
rctest -s -b 1 -N 1024 <addr> (sender, client)
and
rctest -d -b 1 (receiver, server)

I see the source code and i put an usleep pause after
the send call in the function void send_mode(int
s)...with this pause all seems work, but when i try to
send packet bigger than 1019 bytes other problem
arises, for example if i send a packet of 1024 bytes
then the packet will be braked in two packets, one of
1019 e the other of 5. In the case i send many packets
bigger than 1019, some data is lost, the receiver
receive less bytes of what are sended.

rfcomm socket must be realiable sequence stream, but
is not so, i can't understand where is the problem, if
mine or Bluez stack's.
Anybody could tell me if he had the same problems!!
I use Fedora Core 2, kernel  2.6.8-1.521 and bluez
libs/utils 2.8.

Thanks
Regards
 Andrea S.


		
___________________________________ 
Nuovo Yahoo! Messenger: E' molto più divertente: Audibles, Avatar, Webcam, Giochi, Rubrica… Scaricalo ora! 
http://it.messenger.yahoo.it


-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      parent reply	other threads:[~2004-10-13 13:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 18:22 [Bluez-users] ms explorer for bluetooth neoclust
2004-10-13  7:21 ` Marcel Holtmann
2004-10-13  9:43   ` neoclust
2004-10-13 10:18     ` Marcel Holtmann
     [not found]       ` <200410131224.13689.n1c0l4s.l3@wanadoo.fr>
2004-10-13 11:52         ` Marcel Holtmann
2004-10-13 22:42           ` neoclust
2004-10-14 11:25             ` Marcel Holtmann
     [not found]               ` <200410141347.28109.n1c0l4s.l3@wanadoo.fr>
2004-10-17 12:01                 ` Marcel Holtmann
2004-10-17 16:46                   ` neoclust
2004-10-13 22:46       ` neoclust
2004-10-14 11:28         ` Marcel Holtmann
     [not found]           ` <200410141348.12452.n1c0l4s.l3@wanadoo.fr>
2004-10-17 12:03             ` Marcel Holtmann
2004-10-13 13:38     ` Paolino paperino [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=20041013133844.49389.qmail@web40627.mail.yahoo.com \
    --to=vonzoltan@yahoo.it \
    --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