| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
OK bluhm sthen
|
| |
|
| |
|
|
|
|
| |
deraadt@ with make obj in regress.
|
|
|
|
|
| |
these tests to make them similar. Use the setup and cleanup
variables.
|
| |
|
| |
|
|
|
|
| |
variables with example IPs from my daily test run.
|
|
|
|
|
| |
with ICMP6 parameter problem by the network stack. This test expects
the ICMP6 packets, so disable pf on the remote machine temporarily.
|
|
|
|
|
| |
ignores such packets. This should avoid some sporadic failures.
While there, use variable names consistently in all tests.
|
|
|
|
|
|
|
|
| |
regress/ and run python to set the IMPORT_PYTHON variable in several
test Makefiles. This results in W^X violations during 'make build'.
Avoid doing that.
ok bluhm
|
|
|
|
| |
This allows to identify such tests by looking at their output.
|
|
|
|
| |
to configure the regression test machines.
|
|
|
|
|
| |
be used as packet id. Now scapy calls nexthopmtu with this name
explicitly in icmp structure.
|
|
|
|
| |
makes the fragment tests work on FreeBSD. From Ilya Bakulin.
|
|
|
|
|
|
|
|
| |
As header scanning is back, there is always a icmp6 parameter problem
response. Add tests that hide the routing header behind an atomic
fragment header to get the RFC 5095 behaviour. One test puts the
routing header into the second fragment so that it cannot be detected
without reassembly.
|
| |
|
|
|
|
|
| |
are configured correctly. Add a scapy test that creates a packet
without routing header to check the setup.
|
|
|
|
|
|
|
|
| |
not installed. Print a warning, explain the problem and skip the
test in this case. Also skip the test if the environment has not
been configured for the remote test target machine. Fix the Makefile
to run the tests with or without an obj directory. Finally link
the netinet6 regression tests into the build.
|
|
|