From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] MTU in l2test
Date: Mon, 03 Jan 2005 12:43:26 +0100 [thread overview]
Message-ID: <1104752606.8894.51.camel@pegasus> (raw)
In-Reply-To: <2de4657605010303287a6eb6db@mail.gmail.com>
Hi Manjunath,
> > > I am using anycom-120 dongles and using the l2test utility. I am also
> > > setting the incoming and outgoing mtu values (imtu and omtu variables)
> > > to the same value, say 65000 bytes. My 'datasize' is about 45000
> > > bytes. I get the error as mentioned above.
> >
> > what is the output of "hciconfig -a" of the Anycom dongle. Check when
> > this error occurs. Do you see it only when calling the send()/write()
> > function? Maybe there is a buffer problem. What do you see with hcidump?
> > Is the MTU correctly negotiated?
>
> hi marcel,
>
> the "hciconfig -a" shows
>
> hci0: Type: USB
> BD Address: 00:0B:0D:30:5D:EA ACL MTU: 120:20 SCO MTU: 64:0
> UP RUNNING PSCAN ISCAN
> RX bytes:114526 acl:28 sco:0 events:15460 errors:0
> TX bytes:4857089 acl:39552 sco:0 commands:1400 errors:0
> Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
> Packet type: DH5
> Link policy:
> Link mode: SLAVE ACCEPT
> Name: ''
> Class: 0x000000
> Service Classes: Unspecified
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0x0 LMP Ver: 1.1 (0x1) LMP Subver: 0x757
> Manufacturer: Silicon Wave (11)
leave the packet types to the default (all on).
> I get this error when i use the send() function to pump the data out.
> May be there is a problem with the HCI buffer. Is there some way to
> add a delay. The L2CAP connection is correctly established and the MTU
> is also correctly negotiated to the set value (65000) as seen in the
> hcidump on both sides.
The problem is maybe inside the l2cap_do_send() kernel function. I never
played with MTUs such big.
You should think about using RFCOMM, because this is a stream and so MTU
less.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-01-03 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 15:01 [Bluez-users] MTU in l2test Manjunath Prabhu
2005-01-02 14:05 ` Marcel Holtmann
2005-01-03 10:47 ` Manjunath Prabhu
2005-01-03 11:00 ` Marcel Holtmann
2005-01-03 11:28 ` Manjunath Prabhu
2005-01-03 11: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=1104752606.8894.51.camel@pegasus \
--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.