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.