[Bluez-devel] SO_ERROR, LM_RELIABLE

[Bluez-devel] SO_ERROR, LM_RELIABLE

[Daryl Van Vorst]

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

Re: [Bluez-devel] SO_ERROR, LM_RELIABLE

[Max Krasnyansky]

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