[Click] wifi problems with click
Peter De Cleyn
peter.decleyn at gmail.com
Thu May 24 04:04:23 EDT 2007
Hi Povilas,
You probably have a mismatch in the decapsulation of the extended
headers. By default , the new madwifi drivers append Prism2 headers,
so you should use Prism2Decap/Encap instead of ExtraDecap.
I tend to use the atheros descriptors, which you can activate by using:
echo '804' > /proc/sys/net/ath0/dev_type
In order to encapsulate/decapsulate, the AthdescDecap and AthdescEncap
elements can be used. This combination works well for me.
hope this helps,
Peter De Cleyn
On 5/23/07, Povilas Germanavicius <germas at gmail.com> wrote:
> Good evening,
>
> I am having a problem with taking packets from wireless device with click. I
> use this kind of input configuration:
> FromDevice(ath0)
> ->ExtraDecap()
> ->FilterTX()
> ->FilterPhyErr()
> ->Classifier(0/08%0c)
> ->WifiDecap()
> ->HostEtherFilter(ath0,DROP_OTHER true, DROP_OWN true)
> ->Strip(14)
> ->CheckIPHeader()
> ->classify::IPClassifier(ip dscp 34,
> ip dscp 46,
> ....
>
> Is it wright? When i send voice and video packets IPClassifier can't see
> them. And is it possible that madwifi driver is working bad - could it be
> that it changes the packets' headers and IPClassifier doesn't recognise
> them?
>
> Regards,
>
> --
> Povilas Germanavičius
> tel. +37067612600
> msn: germasss at hotmail.com
> skype: povilasgermas
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>
More information about the click
mailing list