From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] PAN with ISSC USB-dongle and MTU
Date: Wed, 25 Jan 2006 11:21:00 +0100 [thread overview]
Message-ID: <1138184460.5782.31.camel@localhost> (raw)
In-Reply-To: <010201c62197$be32dae0$14141bac@mgpi.de>
Hi Bernhard,
> I recently bought 2 mini class-1 bluetooth dongles, and they turned out to
> use the ISSC chip.
>
> It was no problem to establish connections with a GPS mouse (rfcomm) and a
> Palm T5 (ppp).
the default L2CAP MTU for RFCOMM connections is 1024 from our side and
most devices cut them down actually. For BNEP we actually try to get a
L2CAP MTU of 1691 for best performance.
> But I had big problems with PAN between a desktop and my venerable compaq
> armada notebook. I could establish a connection, ping worked. But each time
> I tried to transfer some real payload the connection died, and with it some
> parts of the bluetooth stack. To restablish the connection most of the time
> it's necessary to restart all bluetooth daemons, sometimes even the dongles
> must be re-plugged.
>
> I started to play with the ping size. 'ping -s 900' works, 'ping -s 1000'
> kills the PAN connection. There was hope! Then I played with MTU (on both
> sides): 'ifconfig bnep0 mtu 1000' solves all my problems (default is
> 1500)!!! With this setting I've a rock solid 75 kByte/s transfer rate over
> ftp. A mtu of 1017 still works, 1018 definitely kills the connection. Then
> the syslog is flooded with:
> > hci_acldata_packet: hci0 ACL packet for unknown connection handle 0
> and some stray
> > hci_usb_rx_complete: hci0 corrupted packet: type 2 count 423
>
> Small oversteps of MTU 1017 are recoverable, but a MTU 1500 kills my
> daemons.
I still hate these chips, because it seems that they are not really
capable of handling big data flows. Even if they are supposed to be and
this should have been verified in the qualification testing. I need to
find the exact chip you have and then do my own testing, but in general
it seems we have no other choice except including some tweaks into the
daemons to deal we bad chips.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-01-25 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 10:11 [Bluez-users] PAN with ISSC USB-dongle and MTU Bernhard Held
2006-01-25 10:14 ` Paulo Matias
2006-01-25 10:22 ` Paulo Matias
2006-01-25 11:07 ` Marcel Holtmann
2006-01-25 10:21 ` 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=1138184460.5782.31.camel@localhost \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.