> * Waskiewicz Jr, Peter P <[EMAIL PROTECTED]>
> 2007-08-15 11:02
> > > There is this very horrible way of using the u32
> classifier with a
> > > negative offset to look into the ethernet header.
> >
> > Based on this, it sounds like u32 using protocol 802_3 is broken?
>
> You might be expect
* Waskiewicz Jr, Peter P <[EMAIL PROTECTED]> 2007-08-15 11:02
> > There is this very horrible way of using the u32 classifier
> > with a negative offset to look into the ethernet header.
>
> Based on this, it sounds like u32 using protocol 802_3 is broken?
You might be expecting too much from u3
> * Waskiewicz Jr, Peter P <[EMAIL PROTECTED]>
> 2007-08-09 18:07
> > My big question is: Has anyone recently used the 802_3
> protocol in tc
> > with u32 and actually gotten it to work? I can't see how the
> > u32_classify() code can look at the mac header, since it is
> using the
> > networ
* Waskiewicz Jr, Peter P <[EMAIL PROTECTED]> 2007-08-09 18:07
> My big question is: Has anyone recently used the 802_3 protocol in tc
> with u32 and actually gotten it to work? I can't see how the
> u32_classify() code can look at the mac header, since it is using the
> network header accessor to
I've recently been trying to use tc with u32 classifiers to filter
ethernet traffic based on ethertype. Although we found and fixed an
issue in the sch_prio call to tc_classify() (thanks Patrick!), this
didn't fix the actual filtering issue. For those of you who are curious
or are tc-savy, I'm re
