| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
OK bluhm sthen
|
| |
|
| |
|
|
|
|
| |
deraadt@ with make obj in regress.
|
|
|
|
| |
of the regress machine.
|
|
|
|
|
| |
these tests to make them similar. Use the setup and cleanup
variables.
|
| |
|
|
|
|
| |
need an allow-opts. Otherwise pf blocks packets with option header.
|
| |
|
|
|
|
|
| |
ignores such packets. This should avoid some sporadic failures.
While there, use variable names consistently in all tests.
|
|
|
|
| |
that "neighbor discovery" confuses the test.
|
|
|
|
|
|
|
|
| |
packet was sent and its reply received before the sniffer was up
and running. So sleep a second after starting the sniffer thread
but before sending the packet. With pf_forward 0m51.54s, pf_fragment
1m33.59s, pf_state 0m03.64s the test are still faster than with
forking.
|
|
|
|
| |
This reduces test execution time from 2m21.95s to 1m09.80s.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
options have changed, tun has been renamed to tap. Adapt tests.
|
|
|
|
|
|
|
|
|
| |
for path MTU discovery. The router behind the pf machine has MTU
1300. The ICMP packet generated by the router matches the pf state
and is NATed correctly. Additionally the pf machine itself has an
interface MTU 1400. So when pf is sending a packet is has to
generate a correct "fragmentation needed" or "packet too big" ICMP
response. This is done with pf route-to and reply-to.
|
|
|
|
|
|
| |
accept inner IPv6 packets in ICMP6 with bad checksum created by pf.
Use same workaround as in pf_forward tests and fork a process for
sniffing.
|
|
|
|
| |
and pf fragment tests in sync.
|
|
|
|
|
|
|
| |
in fragments to a machine running pf. From there it is forwarded
with route-to to a router with a smaller MTU. Path MTU discovery
has to make successive fragments shorter and pf route-to has to
preserve the fragment size.
|
| |
|
| |
|
|
|
|
| |
makes the fragment tests work on FreeBSD. From Ilya Bakulin.
|
|
|
|
|
| |
only. Change address layout and add individual tests for each
feature rdr-to and nat-to and rdr-to together with nat-to.
|
|
|
|
|
|
| |
checksum of a NATed UDP or TCP packet in the payload of an ICMP
packet anymore. Disable all test that rely on this feature.
Check that the router's interface mtu has been set to 1300.
|
|
|
|
| |
remote test machine.
|
|
|
|
| |
softly if the setup is incomplete. Link them to the build.
|
|
|
|
|
| |
run over 4 machines. Add a check-setup target to verify that
interface addresses and routes are properly set up.
|
|
|
|
|
|
| |
initial Path-MTU discovery packet.
OK bluhm@
|
|
|
|
| |
the shell.
|
| |
|
| |
|
|
|
|
| |
packet with overlaps. Adapt existing tests.
|
|
|
|
|
| |
Some fragments contain invalid data, this must be replaced to
reassemble a valid packet.
|
|
You have to setup four machines manually as described in the makefile.
The test uses scapy and python to send ping echo request or udp
echo packets along the routers. It analyzes the returned ping echo
reply or udp packets or the icmp error packets.
|