This test illustrates the use of scapy to test pf.
This builds on https://reviews.freebsd.org/D12580
Details
Details
- Reviewers
asomers - Group Reviewers
tests network - Commits
- rS324376: pf: Very basic forwarding test
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 11906
Event Timeline
tests/sys/netpfil/pf/forward.sh | ||
---|---|---|
26 | Here as in the other review, use RFC5737 addresses | |
34 | This is too intrusive, and could screw up the host system. If you're going to do it, then put require.config allow_sysctl_side_effects in the head, and restore the old setting of net.inet.ip.forwarding during cleanup. | |
tests/sys/netpfil/pf/pft_ping.py | ||
2 | Is it python2 or python3? |
tests/sys/netpfil/pf/forward.sh | ||
---|---|---|
34 | Oh, I see. I didn't realize that was a per-VIMAGE sysctl. |
tests/sys/netpfil/pf/forward.sh | ||
---|---|---|
12 | require.progs searches through your PATH so it should be used with plain executable names. require.files does not, so it should be used with absolute paths. In this case, since ports can be installed to alternate prefixes, you should probably do require.progs scapy |