From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] ISSC USB dongle can't ping with size 1000
Date: Thu, 23 Feb 2006 11:57:48 +0100 [thread overview]
Message-ID: <1140692268.24721.22.camel@localhost> (raw)
In-Reply-To: <E64BAD5A8AD46740828069A678D9DD73011B03@netbe01.net.unimis>
Hi Al,
> I have the same problem as below which was posted last month.
>
> > 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.
>
> I wonder if there is other solutions to this problem cause the above solution needs to set MTU to 1000 on both sides.
>
> I try ISSC dongle with IVT software as NAP on Windows XP. Ping with size
> 1500 works fine. It seems ISSC chip has some problems to work with BlueZ, in
> addition to adding HCI_RESET.
I am pretty sure that your chip is at fault here. I have no internals
about your chip, but whatever buffer size you tell us, we will use. And
BlueZ will use it as fast as possible. The latency is very low and the
HCI flow control works fine. So I assume there exists a race condition
in your side of the HCI flow control implementation which triggers a
problem. You can verify with hcidump that we do everything right. The
faulty application is actually not BNEP here. I think you can reproduce
it with any program sending big L2CAP packets. So a test setup with
l2test and different MTU might trigger it more easily.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-23 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 8:44 [Bluez-users] ISSC USB dongle can't ping with size 1000 Al
2006-02-23 10:57 ` Marcel Holtmann [this message]
2006-02-23 11:23 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2006-02-24 11:14 Al
2006-03-09 2:01 Al
2006-03-09 13:49 ` Marcel Holtmann
2006-03-13 4:48 Al
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=1140692268.24721.22.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox