#
1.6 |
|
01-Feb-2021 |
bluhm |
Syntax of pf(4) route-to has changed. Adapt tests.
|
Revision tags: OPENBSD_6_3_BASE OPENBSD_6_4_BASE OPENBSD_6_5_BASE OPENBSD_6_6_BASE OPENBSD_6_7_BASE OPENBSD_6_8_BASE
|
#
1.5 |
|
11-Jan-2018 |
bluhm |
Add tests for incoming route-to and outgoing reply-to rules. Disable the cases that currently fail.
|
Revision tags: OPENBSD_5_9_BASE OPENBSD_6_0_BASE OPENBSD_6_1_BASE OPENBSD_6_2_BASE
|
#
1.4 |
|
24-Aug-2015 |
bluhm |
Extend the pf forward and fragment tests with a second challenge 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.
|
#
1.3 |
|
17-Aug-2015 |
bluhm |
Add forwarding tests for pf route-to and reply-to. Keep pf forward and pf fragment tests in sync.
|
Revision tags: OPENBSD_5_6_BASE OPENBSD_5_7_BASE OPENBSD_5_8_BASE
|
#
1.2 |
|
18-Jul-2014 |
bluhm |
The pf forward tests were running rdr-to and nat-to simultaneously only. Change address layout and add individual tests for each feature rdr-to and nat-to and rdr-to together with nat-to.
|
#
1.1 |
|
12-Jul-2014 |
bluhm |
Automatically load the required pf rules into the kernel of the remote test machine.
|
#
1.5 |
|
11-Jan-2018 |
bluhm |
Add tests for incoming route-to and outgoing reply-to rules. Disable the cases that currently fail.
|
Revision tags: OPENBSD_5_9_BASE OPENBSD_6_0_BASE OPENBSD_6_1_BASE OPENBSD_6_2_BASE
|
#
1.4 |
|
24-Aug-2015 |
bluhm |
Extend the pf forward and fragment tests with a second challenge 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.
|
#
1.3 |
|
17-Aug-2015 |
bluhm |
Add forwarding tests for pf route-to and reply-to. Keep pf forward and pf fragment tests in sync.
|
Revision tags: OPENBSD_5_6_BASE OPENBSD_5_7_BASE OPENBSD_5_8_BASE
|
#
1.2 |
|
18-Jul-2014 |
bluhm |
The pf forward tests were running rdr-to and nat-to simultaneously only. Change address layout and add individual tests for each feature rdr-to and nat-to and rdr-to together with nat-to.
|
#
1.1 |
|
12-Jul-2014 |
bluhm |
Automatically load the required pf rules into the kernel of the remote test machine.
|