RE: Potential u32 classifier bug.

2007-08-15 Thread Waskiewicz Jr, Peter P
> * 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

Re: Potential u32 classifier bug.

2007-08-15 Thread Thomas Graf
* 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

RE: Potential u32 classifier bug.

2007-08-15 Thread Waskiewicz Jr, Peter P
> * 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

Re: Potential u32 classifier bug.

2007-08-15 Thread Thomas Graf
* 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