History log of /openbsd/regress/sys/netinet/frag/Makefile (Results 1 – 11 of 11)
Revision Date Author Comments
# 973a6851 22-May-2021 bluhm <bluhm@openbsd.org>

Test more corner cases of IPv4 fragment reassembly.


# 70788dfd 30-Dec-2020 kn <kn@openbsd.org>

py3-scapy is now scapy

OK bluhm sthen


# 6ba48214 25-Dec-2020 bluhm <bluhm@openbsd.org>

Send fragment that reaches beyond max packet length. pf ignores
it, but stack somehow puts it into the fragment queue.


# 647ac401 25-Dec-2020 bluhm <bluhm@openbsd.org>

Switch to scapy with python 3.


# b5d99089 17-Dec-2020 bluhm <bluhm@openbsd.org>

Remove echo headlines.


# fa6bead2 15-Jan-2020 bluhm <bluhm@openbsd.org>

Do not create files as dependency of .BEGIN rule. Noticed by
deraadt@ with make obj in regress.


# f39ab060 10-May-2019 bluhm <bluhm@openbsd.org>

Simplify the detection for installed python and scapy. Refactor
these tests to make them similar. Use the setup and cleanup
variables.


# 76ee45ff 10-Sep-2018 bluhm <bluhm@openbsd.org>

Send many small fragments that exceed the pf reassembly queue limit.


# 1e0c3835 30-Aug-2018 bluhm <bluhm@openbsd.org>

Use correct environment variable to access remote machine.


# 0b163fd1 15-Sep-2017 bluhm <bluhm@openbsd.org>

Clean up pf rules and states on remote machine so that they do not
interfere with later tests.


# 3fe81ad4 07-Sep-2017 bluhm <bluhm@openbsd.org>

Copy IPv6 fragment test cases to IPv4 and adapt to the different
behavior. All tests are run once with pf fragment reassembly and
once with pf disabled and IP input reassembly. Three sub tests are

Copy IPv6 fragment test cases to IPv4 and adapt to the different
behavior. All tests are run once with pf fragment reassembly and
once with pf disabled and IP input reassembly. Three sub tests are
currently disabled as the IP stack behaves differently than pf.

show more ...