netpfil tests: run in parallel

Run these tests in their own (vnet) jail so we don't have to worry about IP
range or jail name conflicts.

Reviewed by:	markj
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D46040

tests/sys/netpfil/common/Makefile

@@ -12,8 +12,9 @@ ATF_TESTS_SH+=	\
 		fragments \
 		forward
 
-# Tests reuse jail names and so cannot run in parallel.
-TEST_METADATA+=	is_exclusive=true
+# Allow tests to run in parallel in their own jails
+TEST_METADATA+= execenv="jail"
+TEST_METADATA+= execenv_jail_params="vnet allow.raw_sockets"
 
 ${PACKAGE}FILES+=	\
 		utils.subr \

tests/sys/netpfil/ipfw/Makefile

@@ -5,4 +5,8 @@ TESTSDIR=       ${TESTSBASE}/sys/netpfil/ipfw
 ATF_TESTS_SH+=	fwd
 ${PACKAGE}FILES+=	fwd_inetd.conf
 
+# Allow tests to run in parallel in their own jails
+TEST_METADATA+= execenv="jail"
+TEST_METADATA+= execenv_jail_params="vnet allow.raw_sockets"
+
 .include <bsd.test.mk>

tests/sys/netpfil/pf/Makefile

@@ -54,8 +54,9 @@ ATF_TESTS_PYTEST+=	frag6.py
 ATF_TESTS_PYTEST+=	nat66.py
 ATF_TESTS_PYTEST+=	sctp.py
 
-# Tests reuse jail names and so cannot run in parallel.
-TEST_METADATA+=	is_exclusive=true
+# Allow tests to run in parallel in their own jails
+TEST_METADATA+= execenv="jail"
+TEST_METADATA+= execenv_jail_params="vnet allow.raw_sockets"
 
 PROGS=	divapp