| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
be used as packet id. Now scapy calls nexthopmtu with this name
explicitly in icmp structure.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
makes the fragment tests work on FreeBSD. From Ilya Bakulin.
|
| |
|
|
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.
|