[Click] the 802.11 MAC protocol

[John Bicket]

Almost all the cards do the management layer of 802.11 (association,
scanning, etc) in firmware. Right now we have elements that can do
things like set the bitrate of packets you send to wireless devices, as
well as get information from received packets like signal and noise.
We also have elements that will push out unicast packets that failed to be
acked by a receiver. See the elements/wifi directory in the checkout.

We're working with a chipset that pushes the management layer into the
device driver, so we can implement access point functionality in click,
but it doesn't work yet and is about 3 months from being usable.

--john




Eddie Kohler [kohler at cs.ucla.edu] wrote:
>Yihong,
>
>Others on this list (John?) will be able to answer this more precisely, but 
>I believe Click relies on the underlying device drivers and nics to 
>implement the 802.11 MAC, as you'd expect.  The elements in elements/wifi 
>are worth a look, though (they interact more closely with the mac).
>
>Why do you need to implement a MAC in Click?
>
>Eddie
>
>
>Yihong Zhou wrote:
>>Hi,
>> 
>>I am a beginner of the click modular router.  I'd like to know how much
>>work needs to be done to implement the 802.11 MAC protocol?  Or is that
>>pragmatic?  Since most of the documents are about how to implement the
>>routing protocols.
>> 
>>Thanks a lot.
>> 
>>_______________________________________________
>>click mailing list
>>click at amsterdam.lcs.mit.edu
>>https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>_______________________________________________
>click mailing list
>click at amsterdam.lcs.mit.edu
>https://amsterdam.lcs.mit.edu/mailman/listinfo/click