| #
1.6 |
|
01-Feb-2021 |
bluhm |
Syntax of pf(4) route-to has changed. Adapt tests.
|
|
Revision tags: OPENBSD_6_2_BASE 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 |
|
07-Jun-2017 |
bluhm |
To test IPv6 fragements with extension header, the pf pass rules
need an allow-opts. Otherwise pf blocks packets with option header.
|
|
Revision tags: OPENBSD_5_9_BASE OPENBSD_6_0_BASE OPENBSD_6_1_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 |
|
13-Aug-2015 |
bluhm |
Add IPv6 fragment tests for pf route-to. A big ping packet is sent
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.
|
|
Revision tags: OPENBSD_5_8_BASE
|
|
| #
1.2 |
|
21-Jul-2015 |
bluhm |
Extend the setup with another address for testing pf route-to.
|
|
Revision tags: OPENBSD_5_6_BASE OPENBSD_5_7_BASE
|
|
| #
1.1 |
|
12-Jul-2014 |
bluhm |
Automatically load the required pf rules into the kernel of the
remote test machine.
|
|
Revision tags: OPENBSD_6_2_BASE
|
|
| #
1.5 |
|
07-Jun-2017 |
bluhm |
To test IPv6 fragements with extension header, the pf pass rules
need an allow-opts. Otherwise pf blocks packets with option header.
|
|
Revision tags: OPENBSD_5_9_BASE OPENBSD_6_0_BASE OPENBSD_6_1_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 |
|
13-Aug-2015 |
bluhm |
Add IPv6 fragment tests for pf route-to. A big ping packet is sent
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.
|
|
Revision tags: OPENBSD_5_8_BASE
|
|
| #
1.2 |
|
21-Jul-2015 |
bluhm |
Extend the setup with another address for testing pf route-to.
|
|
Revision tags: OPENBSD_5_6_BASE OPENBSD_5_7_BASE
|
|
| #
1.1 |
|
12-Jul-2014 |
bluhm |
Automatically load the required pf rules into the kernel of the
remote test machine.
|