Hi,
Thanks for the report!
What exact kernel version are you testing?
We can offer advice, but I'm afraid our team does not have cycles to track down and fix those test failures in your environment.
In some cases, you will probably want to update your environment. For example, I would recommend enabling CONFIG_SYN_COOKIES, since that should give a much more robust and typical Linux TCP stack.
In other cases, your kernels may have different behavior, for various reasons (local patches or atypical .config), that will require you to modify the tests to expect your behavior.
In other cases the upstream net-next behavior may have diverged from what these tests in the github packetdrill repo expect. If someone in the Linux networking community wants to submit pull requests to update the tests to expect the latest net-next behavior, we are happy to review and merge those. Our team has cycles to maintain our internal branches of these tests to match the behavior in our environment, but unfortunately does not have time to strictly keep all upstream tests up-to-date with respect to matching net-next behavior.
best,
neal