> Waskiewicz Jr, Peter P wrote: > >>The protocol match is on skb->protocol, so it case of > ethernet its on > >>the ethernet protocol, which is ETH_P_IP or "ip" for IPv4. > > > > > > I see that in the code, but the reason I started worrying was when I > > added the 802_3 classifier on 8 flows, it would shove all > traffic into > > flowid 1:1, no matter if it matched or not. > > > > I'll keep investigating and see if I can narrow down what > I'm seeing. > > > I'm not sure what you're expecting. skb->protocol is usually not set > to ETH_P_802_3, which is why the filter is not matching.
I understand that. I had two issues, which you cleared up one by reminding me that the protocol matches on skb->protocol before it tries to run the ->classify() routine. The other issue I am seeing is with 8 bands, an 802_3 filter is affecting classification of IP traffic. For example, I have an 802_3 filter to look for dst MAC address, but an ssh packet, which without any filters should go into flowid 1:3 on my system, is getting pushed into flowid 1:1. I remove the 802_3 filter, and ssh traffic starts going back into 1:3. No other filters on the system. That's the main issue I'm seeing, so I'll keep investigating to see what's going on. -PJ - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
