[Bluez-devel] Patch for L2CAP (kernel<->userspace)

[Bluez-devel] Patch for L2CAP (kernel<->userspace)

[Matthias]

>Date: 2005-01-25 12:54:00 GMT (11 weeks, 1 day and 49 minutes ago)  
>Hi Matthias,  
  
>> I have a (problem) with the L2CAP layer from BlueZ.  
>> I wrote a program that communicates with a mobile phone by using its own  
L2CAP   
>> layer (the program builds its own L2CAP packets for protocol testing).  
>> For example I send a valid "connection request" to that phone and the phone   
>> answers with a valid "connection response".  
>> So far so good.   
>> But then the L2CAP layer from BlueZ sends a "command reject", because this   
>> layer doesn´t know about the "connection request" and cannot handle   
>> the "connection response".  
>> Ok, i understand that.   
>> But has anybody an idea how i can communicate with my own L2CAP layer and  
the   
>> phone only without using the BlueZ L2CAP layer, because the Bluez layer  
always   
>> prevents a further communication?  
>> Hmm... is in this case the L2CAP RAW socket the solution?  
>> I´m stucked with that problem and i hope anybody as an idea.  
  
>as Xavier mentioned the easiest solution is to unload the L2CAP kernel  
>module. However I looked at the code and it seems that the the kernel  
>respond to packets with all idents. It should not do that, because they  
>are shared between the kernel and the userspace. I think a patch for  
>that is needed so that for commands from the RAW socket no responses are  
>send.  
  
>Regards  
  
>Marcel  
 
Hi Marcel,  
  
once i posted a question dealing with an aborted L2CAP communication.  
  
The solution is, that "a patch for that problem is needed so that for commands  
from the RAW socket no responses are send."  ("However I looked at the code  
and it seems that the the kernel respond to packets with all idents. It should  
not do that, because they are shared between the kernel and the userspace.")  
  
Since iam a noob programmer i want to ask, if the problem is already fixed in  
a newer patch or is the problem still existent.  
  
greetings  
Matthias  
 
 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Patch for L2CAP (kernel<->userspace)

[Marcel Holtmann]

Hi Matthias,

> The solution is, that "a patch for that problem is needed so that for commands  
> from the RAW socket no responses are send."  ("However I looked at the code  
> and it seems that the the kernel respond to packets with all idents. It should  
> not do that, because they are shared between the kernel and the userspace.")  
>   
> Since iam a noob programmer i want to ask, if the problem is already fixed in  
> a newer patch or is the problem still existent.  

I thought about fixing this, but at the moment it isn't done. Feel free
to send in a patch for it, because I am busy with other stuff and the
whole SCM/Bitkeeper/GIT thing is not really helping right now.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel