From: Marcel Holtmann <marcel@holtmann.org>
To: aquamala@o2.pl
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] l2test: Send failed. Invalid argument(22)
Date: Thu, 06 May 2004 23:11:01 +0200 [thread overview]
Message-ID: <1083877861.4420.84.camel@pegasus> (raw)
In-Reply-To: <20040506204859.GA2483@reynevan>
Hi Przemek,
> I'm trying to test (almost) my implementation of L2CAP.
> This is what i do:
>
> $ ./l2test -s -N 20 -S 00:0A:3A:53:12:4A 00:80:37:16:30:8B
>
> Unfortunetly, I get:
>
> l2test[2445]: Connected [imtu 672, omtu 512, flush_to 65535]
> l2test[2445]: Sending ...
> l2test[2445]: Send failed. Invalid argument(22)
>
> No data is send. Just after L2CAP connection is established my
> module is receiving Disconnection Request packet.
>
> Please, tell me, what does that "Invalid argument(22)" mean.
you are using BlueZ to test your own implementation of L2CAP. Sounds
nice, but you already got all you need. Run hcidump and see what is
going on the HCI level. If you are looking for the error code than check
errno and the L2CAP source code. From a quick view it looks like your
data is bigger than your MTU. L2CAP is sequential packet and not a
stream.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-06 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 20:48 [Bluez-users] l2test: Send failed. Invalid argument(22) Przemek
2004-05-06 21:11 ` Marcel Holtmann [this message]
2004-05-06 22:13 ` Przemek
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=1083877861.4420.84.camel@pegasus \
--to=marcel@holtmann.org \
--cc=aquamala@o2.pl \
--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