From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] ISSC USB dongle with PAN
Date: Thu, 23 Feb 2006 11:43:57 +0100 [thread overview]
Message-ID: <1140691437.24721.14.camel@localhost> (raw)
In-Reply-To: <004a01c63829$20f79970$1f1410ac@AL31>
Hi Al,
> I am trying NAP using an ISSC USB dongle. On the PANU side I use
> CRS chip with IVT software on Windows XP.
>
> The bnep0 connection can be established. Ping with size 900
> works. But
> Ping with size 1000 doesn't work. CSR dongle works fine with same
> bluez software.
>
> I have searched for the list and found othershave similiar problems.In
> addition to set
> MTU to 1000(ifconfig bnep0 mtu 1000), a ny other solutions to this
> problems?
> Does MTU solution must be done on both sides (NAP and PANU)?
according to your email address, you work for ISSC. So you might wanna
ask some of your colleges why we can't send big packets with the ISSC
chip. I haven't found any bug in the BlueZ HCI layer, but if the data
packet is too big then your HCI goes spooky. From my understanding it is
a bug in your chip (most likely the HCI part of your firmware).
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-02-23 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 3:27 [Bluez-devel] ISSC USB dongle with PAN Al Chane
2006-02-23 10:43 ` 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=1140691437.24721.14.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).