From: "Daryl Van Vorst" <daryl@wideray.com>
To: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] SO_ERROR, LM_RELIABLE
Date: Tue, 27 May 2003 13:35:29 -0700 [thread overview]
Message-ID: <001001c3248f$838dfdf0$1a01010a@baked> (raw)
Max,
I'm working on LM_RELIABLE support in l2test. I'm using aclsession to send
both valid and invalid l2cap packets.
I'm sending an invalid (wrong length) packet followed by a valid packet. I
get the ECOMM error and clear it with getsockopt(SO_ERROR), and then I can
receive the next packet. That works fine for both long and short packets.
But when I disconnect, I get the following in syslog (for either the too
long or the too short case):
l2test[583]: Disconnect. Communication error on send
Normally that would say "Disconnect. Success".
But I'm not sending. (At least not that I know of) Any ideas about what
would cause that?
The same code will print "Disconnect. Success" if aclsession is used to sen=
d
two valid packets.
-Daryl.
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2003-05-27 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 20:35 Daryl Van Vorst [this message]
2003-06-12 17:13 ` [Bluez-devel] SO_ERROR, LM_RELIABLE Max Krasnyansky
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='001001c3248f$838dfdf0$1a01010a@baked' \
--to=daryl@wideray.com \
--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