summaryrefslogtreecommitdiffstats
path: root/regress/sys/net/pf_fragment (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Syntax of pf(4) route-to has changed. Adapt tests.bluhm2021-02-012-6/+6
|
* py3-scapy is now scapykn2020-12-301-3/+3
| | | | OK bluhm sthen
* Switch to scapy with python 3.bluhm2020-12-2518-177/+177
|
* Remove echo headlines.bluhm2020-12-171-22/+1
|
* Do not create files as dependency of .BEGIN rule. Noticed bybluhm2020-01-151-3/+3
| | | | deraadt@ with make obj in regress.
* Rework when tests have to be skipped due to insufficient configurationbluhm2020-01-081-4/+19
| | | | of the regress machine.
* Simplify the detection for installed python and scapy. Refactorbluhm2019-05-101-49/+44
| | | | | these tests to make them similar. Use the setup and cleanup variables.
* Remove useless make depend targets.bluhm2017-07-071-3/+1
|
* To test IPv6 fragements with extension header, the pf pass rulesbluhm2017-06-071-4/+4
| | | | need an allow-opts. Otherwise pf blocks packets with option header.
* Fix typo in variable name.bluhm2017-01-242-2/+2
|
* Do not use privileged or NFS source ports for UDP packets as inetdbluhm2017-01-1817-71/+99
| | | | | ignores such packets. This should avoid some sporadic failures. While there, use variable names consistently in all tests.
* During sniffing filter strictly on icmp6 "packet too big" to avoidbluhm2016-10-202-1/+6
| | | | that "neighbor discovery" confuses the test.
* By removing all the sleeps I created a race in the pf tests. Thebluhm2016-10-2012-0/+12
| | | | | | | | 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.
* Replace fork() and sleep() with a Python thread for sniffing packets.bluhm2016-10-2012-92/+212
| | | | This reduces test execution time from 2m21.95s to 1m09.80s.
* The clean:, cleandir:, and obj: targets of src/Makefile descend intotb2016-10-191-1/+3
| | | | | | | | 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
* Print SKIPPED if a regress test cannot be executed for some reason.bluhm2016-09-021-1/+3
| | | | This allows to identify such tests by looking at their output.
* Split the check-setup target into smaller parts to make it easierbluhm2016-08-311-6/+14
| | | | to configure the regression test machines.
* comment typossthen2016-05-281-8/+8
|
* Fix tests: Restrict getpid() to lower 16 bit so that it can stillbluhm2016-05-2217-18/+18
| | | | | be used as packet id. Now scapy calls nexthopmtu with this name explicitly in icmp structure.
* Route output to local addresses has changed, ping6 command linebluhm2015-11-011-14/+14
| | | | options have changed, tun has been renamed to tap. Adapt tests.
* Extend the pf forward and fragment tests with a second challengebluhm2015-08-246-19/+31
| | | | | | | | | 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.
* Enable path MTU test with ping for IPv6. Scapy srp1() does notbluhm2015-08-242-8/+18
| | | | | | 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.
* Add forwarding tests for pf route-to and reply-to. Keep pf forwardbluhm2015-08-171-20/+30
| | | | and pf fragment tests in sync.
* Add IPv6 fragment tests for pf route-to. A big ping packet is sentbluhm2015-08-132-24/+32
| | | | | | | 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.
* Extend the setup with another address for testing pf route-to.bluhm2015-07-212-12/+27
|
* When test pf.conf changes, check its syntax and use the new one.bluhm2015-07-201-2/+3
|
* Use a simpler expression to check the ether type in scapy. Thisbluhm2014-12-1916-16/+16
| | | | makes the fragment tests work on FreeBSD. From Ilya Bakulin.
* The pf forward tests were running rdr-to and nat-to simultaneouslybluhm2014-07-181-4/+4
| | | | | only. Change address layout and add individual tests for each feature rdr-to and nat-to and rdr-to together with nat-to.
* Make the pf_fragment test pass again. pf does not adjust thebluhm2014-07-131-15/+15
| | | | | | 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.
* Automatically load the required pf rules into the kernel of thebluhm2014-07-122-34/+51
| | | | remote test machine.
* Teach these pf regress tests to run with obj directory and to failbluhm2014-07-121-26/+51
| | | | softly if the setup is incomplete. Link them to the build.
* Use a saner and consistent address layout for my network tests thatbluhm2014-07-121-77/+139
| | | | | run over 4 machines. Add a check-setup target to verify that interface addresses and routes are properly set up.
* Fix run-regress-fragping to use ping(8) instead of ping6(8) to send thelteo2013-10-171-2/+2
| | | | | | initial Path-MTU discovery packet. OK bluhm@
* Do not write spaces around = in addr.py so it can also be read bybluhm2012-07-101-6/+6
| | | | the shell.
* Kill trailing whitespaces.bluhm2012-07-1018-19/+19
|
* Add addr.py to CLEANFILES.bluhm2012-07-081-2/+2
|
* According to RFC 5722 we drop all IPv6 fragments that belong to abluhm2012-01-134-29/+30
| | | | packet with overlaps. Adapt existing tests.
* Add tests for pf fragment reassembly with all kinds of overlapping.bluhm2011-09-2112-2/+664
| | | | | Some fragments contain invalid data, this must be replaced to reassemble a valid packet.
* Add a test suite to route ip fragments through a box running pf.bluhm2011-09-197-0/+390
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.