From: Max Krasnyansky <maxk@qualcomm.com>
To: "Daryl Van Vorst" <daryl@wideray.com>,
"BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SO_ERROR, LM_RELIABLE
Date: Thu, 12 Jun 2003 10:13:33 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030612101029.0789e508@unixmail.qualcomm.com> (raw)
In-Reply-To: <001001c3248f$838dfdf0$1a01010a@baked>
At 01:35 PM 5/27/2003, Daryl Van Vorst wrote:
>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?
That what you'd get if you do strerror(ECOMM) :(. So the error message is ok.
The question is why do you get error after you cleared it with getsockopt(SO_ERROR).
I'll take a look at it.
Max
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-06-12 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 20:35 [Bluez-devel] SO_ERROR, LM_RELIABLE Daryl Van Vorst
2003-06-12 17:13 ` Max Krasnyansky [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=5.1.0.14.2.20030612101029.0789e508@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
/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