The 82599 data sheet says, that masks must match for all the filters. If so, how do I filter traffic, using Perfect Filters?
I'm reading the data sheet now, here is are the exact words " The 82599 supports masking / range for the previously described fields. These masks are defined globally for all filters in the FDIR...M register. " ^^ Kind of looks like masks must be the same for IP src, dst, port src and port dst. Would not make the filtering impossible, or restricted to a few simple cases? Say, I want to do something to traffic between 1.2.3.0/24 source any port and 5.6.7.8/32 destination port 80, protocol TCP - redirect to a queue number 50 or just drop it (with the -1 queue number). And then I have some completely different rule, where I care about source port and not the destination port, for example, etc. The "all masks must be the same" requirement makes it impossible, unless I'm reading something wrong. I hope I do! Even trying to do something simple like this fails with an error ethtool -N eth4 flow-type tcp4 dst-port 514 action -1 Added rule with ID 2045 ethtool -N eth4 flow-type tcp4 src-port 514 action -1 rmgr: Cannot insert RX class rule: Invalid argument Could you give some examples? 1. How do I drop traffic from subnet A to subnet (or host) B port C and the return traffic as well? 2. How would the first rule be different for host instead of subnets? 3. Can I mix hosts and subnets? 4. Let's say I want to ignore traffic between all hosts on a range of ports - is it supported? ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
