public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Michel Planques <mplanque@laas.fr>
Cc: grpmind+bluez.users@boromir.vpop.net,
	BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] How to configure a 723kbps connection?
Date: Mon, 16 Feb 2004 23:58:12 +0100	[thread overview]
Message-ID: <1076972291.2840.57.camel@pegasus> (raw)
In-Reply-To: <2338.82.255.26.193.1076970003.squirrel@www.laas.fr>

Hi Michel,

> l2test is a good tool to generate Bluetooth traffic between 2 linux
> stations. You can also use the PAN profile with bnep protocol and a
> TCP/UDP traffic generator : I suggest iperf (it works on Linux and
> Windows). I followed these two methods and the results were similar.

of course l2test is one of the best tools, but in case of some iPAQ's
you have the problem that the UART is too slow and you will never reach
the full Bluetooth bandwidth ;)

> I had some bad experiences with the packet type choosen by my dongle's
> link manager. I had to force the packet type to DH5 reach the maximum bit
> rate.

This is one of the biggest problem with bad link managers. I have seen
this very often :(

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-02-16 22:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 17:06 [Bluez-users] How to configure a 723kbps connection? grpmind+bluez.users
2004-02-15 14:33 ` Marcel Holtmann
2004-02-16 22:20   ` Michel Planques
2004-02-16 22:58     ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-17  3:42 grpmind+bluez.users
2004-02-17 11:52 ` Marcel Holtmann
2004-02-17 16:18   ` Steven Singer
2004-02-17 17:03     ` Marcel Holtmann
2004-02-17 22:11       ` Steven Singer
2004-02-17 22:51         ` Marcel Holtmann
2004-02-17  6:36 grpmind+bluez.users
2004-02-17 15:37 ` Marcel Holtmann
     [not found] <lists.bluez.users.40323EC2.8080203@csr.com>
2004-02-17 10:50 ` grpmind+bluez.users
2004-02-17 18:58   ` Marcel Holtmann
     [not found] <200402160913.i1G9DCP02222@webserver.restinfor.pt>
2004-02-17 20:06 ` Paulo Marques
     [not found] <lists.bluez.users.40327430.2090807@grupopie.com>
2004-02-17 20:45 ` Matthew Reimer
     [not found] <lists.bluez.users.1077061006.2665.141.camel@pegasus.SOMEWHERE>
     [not found] ` <lists.bluez.users.4032E137.7080902@vpop.net>
2004-02-18  3:56   ` Matthew Reimer
     [not found] <lists.bluez.users.1077037423.2665.72.camel@pegasus.SOMEWHERE>
     [not found] ` <lists.bluez.users.403291AD.7080601@csr.com>
2004-02-17 23:09   ` Matthew Reimer
2004-02-17 23:36     ` Marcel Holtmann
2004-02-18  3:51       ` Matthew Reimer
2004-02-24  3:49   ` Matthew Reimer
2004-02-25 15:03     ` Paulo Marques

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=1076972291.2840.57.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=grpmind+bluez.users@boromir.vpop.net \
    --cc=mplanque@laas.fr \
    /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