<html>
    <head>
      <base href="https://bugs.dpdk.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8" class="bz_new_table">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED - Traffic filtering when capturing packets"
   href="https://bugs.dpdk.org/show_bug.cgi?id=1349">1349</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Traffic filtering when capturing packets
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DPDK
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>major
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>dts
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>dev@dpdk.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>juraj.linkes@pantheon.tech
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>juraj.linkes@pantheon.tech, probb@iol.unh.edu
          </td>
        </tr>

        <tr>
          <th>Target Milestone</th>
          <td>---
          </td>
        </tr></table>
      <p>
        <div class="bz_comment_block">
          <pre class="bz_comment_text">We currently have a solid solution in the scatter test suite patch. The
filtering is not the main thrust of the patch so it doesn't provide a fully
fleshed out solution.

We should think about the following:
- The solution covers the main use cases, probably what's needed for labs,
- We must document what we're filtering and warn that if a setup deviates (e.g.
there's extra traffic that's not going to be filtered) there could be related
test failures,
    - Related to the above, we could add a config option for extra default
filtering.
- The solution must be abstracted properly so it's easily implementable for all
capturing traffic generators.
          </pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
      <div itemscope itemtype="http://schema.org/EmailMessage">
        <div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
          
          <link itemprop="url" href="https://bugs.dpdk.org/show_bug.cgi?id=1349">
          <meta itemprop="name" content="View bug">
        </div>
        <meta itemprop="description" content="Bugzilla bug update notification">
      </div>
    </body>
</html>