d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

pf tests: Verify that pf limits the number of fragments per packet

Browse Source 
Test the limitation on number of frames per packet introduced in pf in r337969.

Sponsored by:	Klara Systems
This commit is contained in:
Kristof Provost 2018-08-17 15:02:58 +00:00
parent a8e93e3cd7
commit 2848a0e2da
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=337971
1 changed files with 44 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
tests/sys/netpfil/pf/fragmentation.sh
View File

@ -2,6 +2,49 @@
. $(atf_get_srcdir)/utils.subr
atf_test_case "too_many_fragments" "cleanup"
too_many_fragments_head()
{
atf_set descr 'IPv4 fragment limitation test'
atf_set require.user root
}
too_many_fragments_body()
{
pft_init
epair=$(pft_mkepair)
pft_mkjail alcatraz ${epair}a
ifconfig ${epair}b inet 192.0.2.1/24 up
jexec alcatraz ifconfig ${epair}a 192.0.2.2/24 up
ifconfig ${epair}b mtu 200
jexec alcatraz ifconfig ${epair}a mtu 200
jexec alcatraz pfctl -e
pft_set_rules alcatraz \
"scrub all fragment reassemble"
# So we know pf is limiting things
jexec alcatraz sysctl net.inet.ip.maxfragsperpacket=1024
# Sanity check
atf_check -s exit:0 -o ignore ping -c 1 192.0.2.2
# We can ping with < 64 fragments
atf_check -s exit:0 -o ignore ping -c 1 -s 800 192.0.2.2
# Too many fragments should fail
atf_check -s exit:2 -o ignore ping -c 1 -s 20000 192.0.2.2
}
too_many_fragments_cleanup()
{
pft_cleanup
}
atf_test_case "v6" "cleanup"
v6_head()
{
@ -70,5 +113,6 @@ v6_cleanup()
atf_init_test_cases()
{
atf_add_test_case "too_many_fragments"
atf_add_test_case "v6"
}