[Click] Issues on click and madwifi

[David Fuste]

OK! :)
Just one more question.
Does madwifi-ng driver have full support in Click?
For example, do SetTXRate,SetTXPower,... Click elements work fine with 
madwifi-ng? or it is necessary to change these parameters via 
madwifi-tools in a shell before executing the Click config file?

Thanks,
david

Torquato Bertani wrote:
> I think that madwifi.stripped doesn't work with click -1.5.0
> You should use madwifi-ng driver in monitor mode with AthdescEncap()
> and AthdescDecap() elements.
>
> Bye
> Thor
>
> On 11/30/06, dfuste at ac.upc.edu <dfuste at ac.upc.edu> wrote:
>   
>> Hi all,
>> I am experiencing troubles using click+madwifi.stripped.
>> I don't know the origin of my errors (my click configuration, an old version of
>> madwifi.stripped...or me:)
>> I am using Debian linux with kernel 2.4.28 with click-1.5.0 and madwifi.stripped
>> (http://pdos.csail.mit.edu/~jbicket/madwifi.stripped/), and I'm trying to run
>> this click configuration in two computers (obviously, each configuration
>> adapted to each computer; my wifi cards and the tun/tape device are well
>> supported):
>>
>> ---------------------------------------------------
>> AddressInfo(safe_addr 6.0.0.1/8 ath0);
>> winfo :: WirelessInfo(BSSID 00:00:00:00:00:00);
>>
>> FromHost(safe, safe_addr, ETHER safe_addr)
>> -> Print(FromHost)
>> -> q :: Queue()
>> -> Print(ToDevice)
>> -> encap :: WifiEncap(0x0, WIRELESS_INFO winfo)
>> -> set_power :: SetTXPower(63)
>> -> set_rate :: SetTXRate(2)
>> -> radiotap_encap :: RadiotapEncap()
>> -> to_dev :: ToDevice(ath0);
>> // -> to_dev :: ToDevice(ath0raw);
>>
>> // from_dev :: FromDevice(ath0raw,
>> from_dev :: FromDevice(ath0,BPF_FILTER "ether[18:4] == 0x08 and ")
>> -> prism2_decap :: Prism2Decap()
>> -> extra_decap :: ExtraDecap()
>> -> radiotap_decap :: RadiotapDecap()
>> -> phyerr_filter :: FilterPhyErr()
>> -> tx_filter :: FilterTX()
>> -> dupe :: WifiDupeFilter()
>> -> wifi_cl :: Classifier(0/08%0c 1/00%03) //nods data
>> -> WifiDecap()
>> -> SetPacketType(HOST)
>> -> Print(ToHost)
>> -> ToHost(safe);
>> ---------------------------------------------------
>>
>> When I run this configuration in Click user level mode, and I perform a ping to
>> some IP 6.0.0.X, I can see the ARP Requests sent by the kernel due to the
>> "Print(FromHost)" element (or, if I add an static entry in the ARP table of the
>> kernel for the corresponding IP, I can see the IP packets sent by the kernel).
>> However, I can't see any packet printed due to the "Print(ToDevice)" element!
>> All packets are buffered in the Queue and never leaves it.
>> As you can see, I am using "ToDevice(ath0)" insead of "ToDevice(ath0raw)", and I
>> suppose this fact can be the problem. Maybe the ToDevice element don't pull the
>> packets of the Queue. However, I can't create an interface ath0raw using the
>> commands listed in the madwifi.stripped web page (sysctl -w dev.ath0.rawdev=1)
>> because I get the following error: "error: 'dev.ath0.rawdev' is an unknown
>> key". And given that I don't know the difference between ath0 and ath0raw, I
>> have used ath0 :(
>>
>> Which is the difference between these two interfaces? Is this the problem of my
>> configuration? How can I create the ath0raw interface? I have found the same
>> problem in internet for many people but I haven't found a good solution.
>> Moreover, is the madwifi.stripped of
>> http://pdos.csail.mit.edu/~jbicket/madwifi.stripped/ via CVS the latest version
>> of a madwifi with support for Click, or is there a new version of madwifi (not
>> madwifi.stripped) which supports Click?
>>
>> I know it is a mail a bit long but I am very confused on this issues...sorry and
>> Thank you very much!!
>> _______________________________________________
>> 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
>