[Click] wifi and madwifi.stripped

[Peter De Cleyn]

This looks very promising and certainly worth a try later one. For the
moment, I implemented a basic infrastrucutre mac in Click which does the job
in combination with the madwifi drivers.

Thanks for the suggestion!

Peter


On 11/2/05, Daniel Henkel <henk at gmx.com> wrote:
>
> Hi Peter,
>
> We are using a modified version of madwifi with the 2.6.11 kernel. It
> is called SoftMac, and it was done here at the University of Colorado
> at Boulder. SoftMac lets you implement new MAC layers and tweak
> parameters to a certain degree. Too bad the HAL is not available in
> source. :)
>
> More info here:
> https://systems.cs.colorado.edu/projects/softmac
>
> It is working, but still in its infancy. Interoperable with Click.
>
> --
> Have a nice day,
> - Daniel.
>
> .....
> Interdisciplinary Telecommunications Program
> University of Colorado at Boulder
> http://AUGNet.colorado.edu
>
> ---- Original Message ----
> From: Peter De Cleyn
> To: John Bicket <jbicket at amsterdam.lcs.mit.edu>,
> click at amsterdam.lcs.mit.edu
> CC:
> Subject: [Click] wifi and madwifi.stripped
>
> Monday, October 31, 2005, 6:12:26 AM, you wrote:
>
> PDC> Is there any news on the madwifi story? I would like to use the
> PDC> madwifi-stripped functionality, but due to other constraints, I'm
> forced to
> PDC> use a 2.6 kernel, for which no click-wifi-patch is available (yet).
>
> PDC> Is there anyone who has successfully deployed a click/madwifi set up
> using a
> PDC> 2.6. kernel and is willing to share its expertise or do you have some
> clues
> PDC> for me to get me started?
>
> PDC> thanks,
>
> PDC> Peter
>
> PDC> On 9/17/05, Bob Keyes <bob at sinister.com> wrote:
> >>
> >>
> >>
> >> On Thu, 12 May 2005, John Bicket wrote:
> >>
> >> > I have been incorporating the changes from the madwifi.stripped
> >> > driver into the actual madwifi driver. As a result, I won't
> >> > be maintaining the madwifi.stripped driver any longer.
> >>
> >> Does this incorporate all the features need for RoofNet? so
> >> madwifi.stripped is no longer required for roofnet, but a somehwat
> modern
> >> version of madwifi? If so, what versions of madwifi have your changes?
> >>
> >> > Instead of making the device driver send and receive raw 802.11
> >> > packets on the normal device (ie. athX), I have added a second
> "phony"
> >> > device to the madwifi driver that handles all of that (called
> athXraw).
> >> > This allows the use of the normal 802.11 stack as well as the ability
> >> > to run other protocols (ie roofnet) at the same time. If you want to
> >> > bypass the normal 802.11 stack you can use monitor mode, which
> >> > still allows packet transmission using the raw interface.
> >> >
> >> > The code is currently in the madwifi BSD branch, which you can
> checkout
> >> > using:
> >> > cvs -z3
> >> -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/madwifi co -r
> >> > BSD madwifi
> >>
> >> Were these changes ever incorporated into the Linux version of madwifi,
> or
> >> is the a canonical way to compile the BSD version of madwifi in Linux?
> >> > You must use a sysctl to activate the rawdevice if you are running
> the
> >> > driver:
> >> > /sbin/sysctl -w dev.ath0.rawdev=1
> >> >
> >> > Also, you can make the rawdevice use headers in addition
> >> > to just 802.11 frames. You can run
> >> > /sbin/sysctl -w dev.ath0.rawdev_type=X
> >> > where X is
> >> > 0: raw 802.11 frames
> >> > 1: prism headers (ie you can use PrismEncap/PrismDecap)
> >> > 2: radiotap headers (ie you can use RadiotapEncap/RadiotapDecap)
> >>
> >> These sysctls are available in my madwifi driver, but I am still
> getting
> >> errors:
> >>
> >> ToDevice(ath0) send: Message too long
> >>
> >> and occasionally:
> >>
> >> ToDevice(ath0) send: Network is down
> >>
> >> and I want to make sure these are not due to using an incorrect version
> of
> >> madwifi
> >> _______________________________________________
> >> click mailing list
> >> click at amsterdam.lcs.mit.edu
> >> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> >>
> PDC> _______________________________________________
> PDC> click mailing list
> PDC> click at amsterdam.lcs.mit.edu
> PDC> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
>