Monitor Mode question

[Clyde McPherson]

Dan:
Yeah, I saw the patch. Thanks a lot for it.

-Tex


> On Tue, 2008-07-29 at 15:50 -0400, Clyde McPherson wrote:
>   
>> Thanks for clearing that up for me.  I knew that was the reason, but
>> my boss said but rtap0 was being created, so it must support
>> monitoring (you know boss'es)!! She believes me now...
>>     
>
> I've posted a patch to linux-wireless that will only create the rtap
> entries if mesh firmware is also used, which should "fix" the issue for
> your hardware by not exposing the rtap stuff at all.
>
> Dan
>
>
>   
>> Thanks for your help
>> Tex
>>
>>
>>     
>>> On Sat, 2008-07-26 at 16:06 -0400, Clyde McPherson wrote:
>>>   
>>>       
>>>> I am using a CF 8386 with the current version of the libertas drivers 
>>>> and I am using the firmware that is downloaded and created by the 
>>>> libertas fwcutter, which seems to be downloaded from the gumstix site. 
>>>> Whenever I echo any hex values to the sysfs lbs_rtap file, the firmware 
>>>> returns a result of 2 and the libertas driver reports an error, but the 
>>>> rtap0 network device is created. When I try to use the rtap0 device via 
>>>> wireshark, kismet, etc. , no packets are being sent over. I guess my 
>>>> question is, since the firmware response is a 2, then monitor mode is 
>>>> not possible? Should the rtap0 device even be created at that time?
>>>>     
>>>>         
>>> No, it shouldn't.  Looks like CMD_802_11_MONITOR_MODE is a usb8388
>>> firmware specific extension, and thus we shouldn't be exposing the rtap
>>> functionality via MONITOR_MODE on non-usb8388 devices.
>>>
>>> dan
>>>
>>>
>>>
>>> _______________________________________________
>>> libertas-dev mailing list
>>> libertas-dev at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/libertas-dev
>>>
>>>   
>>>       
>
>
> _______________________________________________
> libertas-dev mailing list
> libertas-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libertas-dev
>
>