netdev - RE: Potential u32 classifier bug.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Aug 2007 11:02:00 -0700
From:	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
To:	"Thomas Graf" <tgraf@...g.ch>
Cc:	<netdev@...r.kernel.org>
Subject: RE: Potential u32 classifier bug.

> * Waskiewicz Jr, Peter P <peter.p.waskiewicz.jr@...el.com> 
> 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 start looking.  I think this is an issue 
> > with the classification code, but I'm looking to see if I'm doing 
> > something stupid before I really start digging into this mess.
> 
> 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 want to look into the cmp ematch which can be 
> attached to almost any classifier. It allows basing offsets 
> on any layer thus making ethernet header filtering trivial.

I'll look at this.  Thanks Thomas for the response!

-PJ
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html