[Click] Click and Wireless Tools

[Douglas S. J. De Couto]

Hi Peter,

As far as I know you can't get the association information through the 
click wifi stuff.  But the roofnet guys (cc'ed) would know, they wrote 
that stuff.  I imagine you need to patch the driver more.

The click wifi stuff could not be done at userlevel, because some of 
the functionality involves getting back a copy of every packet that was 
sent.  But for low-bandwidth stuff like association events, I am sure 
you can get it to work at both kernel and userlevel, especially if 
linux has a good interface for it already.

I don't think there is any more documentation other than the patches 
and element code itself.

d


On 20 May 2004, at 15:20, Peter De Cleyn wrote:

> Hi doug,
>
> Thanks for your answer!
>
> I already saw the wifi elements, but I haven't got time to inspect them
> more carefully. I see kernel patches are provided for aironet and 
> hostap.
> I also plan to use the hostAP driver. In a first approach I only need 
> to be
> able to get the association data (l2 address of access point etc) from
> the driver. Could you tell me if this is already possible with these
> patches or should I patch the driver some more?
>
> The easiest way for now is probably an userlevel element, but in the 
> long
> run I would prefer running my configuration in kernel space.
>
> Any hints on how to proceed are welcome.
>
> Peter
>
> BTW does there exist some more documentation about the wifi patches and
> elements?
>
>  ______________
> /Peter De Cleyn\
> -------------------------------------
> University of Antwerp
> Dep. Math. and Computer Science
> PATS research group
> -------------------------------------
> Middelheimlaan 1
> Building G
> B-2020 Antwerp
> -------------------------------------
> http://www.ua.ac.be
> http://win-www.ruca.ua.ac.be
> peter.decleyn at ua.ac.be
> +32 3 265 33 64
>
>
> On Thu, 20 May 2004, Douglas S. J. De Couto wrote:
>
>> Hi Peter,
>>
>> You can put any code you like in an element.  However, if it calls a
>> userlevel library, it will only run in userlevel click, and needs to
>> have ELEMENT_REQUIRES(userlevel) at the end of the element code.
>> Similarly, if it relies on kernel code, it will only run in kernel
>> click.
>>
>> We have some elements that tightly integrate with wireless devices in
>> the kernel, but the do require patching the device drivers and kernel
>> in some cases; see the elements in in elements/wifi, especially
>> WifiTXFeedback. It would be great if there were some elements that
>> talked to the more general wireless library.
>>
>> - doug
>>
>> On 19 May 2004, at 13:47, Peter De Cleyn wrote:
>>
>>> Hi all,
>>>
>>> I want to incorporate some L2 information of a wireless interface 
>>> (like
>>> association events etc) in to a Click router configuration. Can I use
>>> the
>>> wireless library (iwlib) to capture events in an element as I would 
>>> do
>>> in
>>> any other application or kernelmodule?
>>>
>>> If not, is there a way to collect and respond to the events available
>>> from
>>> the Wireless Events subsystem?
>>>
>>> many thanks,
>>>
>>> Peter
>>>
>>>  ______________
>>> /Peter De Cleyn\
>>> -------------------------------------
>>> University of Antwerp
>>> Dep. Math. and Computer Science
>>> PATS research group
>>> -------------------------------------
>>> Middelheimlaan 1
>>> Building G
>>> B-2020 Antwerp
>>> -------------------------------------
>>> http://www.ua.ac.be
>>> http://win-www.ruca.ua.ac.be
>>> peter.decleyn at ua.ac.be
>>> +32 3 265 33 64
>>>
>>> _______________________________________________
>>> click mailing list
>>> click at amsterdam.lcs.mit.edu
>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>>
>> --
>> Douglas S. J. De Couto    <decouto at csail.mit.edu>
>>
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
--
Douglas S. J. De Couto    <decouto at csail.mit.edu>