vnet tests: verify that we can load if_epair and if_bridgeWe're going to start running many of the vnet tests in nested jails (so theycan run in parallel). That means the tests won't be able to lo
vnet tests: verify that we can load if_epair and if_bridgeWe're going to start running many of the vnet tests in nested jails (so theycan run in parallel). That means the tests won't be able to load kernel modules,which we commonly do for if_epair and if_bridge.Just assume that all vnet tests need this, because so many of them do that wedon't want to manually annotate all of them.This is essentially a no-op on non-nested tests.Do the same for the python test framework.While here also have pflog_init actually call pft_init. While having pflogloaded implies we have pf too pft_init also checks for vimage support, and nowfor if_epair.Reviewed by: markjMFC after: 1 monthSponsored by: Rubicon Communications, LLC ("Netgate")Differential Revision: https://reviews.freebsd.org/D46039(cherry picked from commit ae8d58814089308028046ac80aeeb9cbb784bd0a)
show more ...
vnet tests: check for if_bridge.koA number of tests create a bridge, but did not check if if_bridge.ko is loaded.We usually get away with that, because `ifconfig bridge create` autoloads themodu
vnet tests: check for if_bridge.koA number of tests create a bridge, but did not check if if_bridge.ko is loaded.We usually get away with that, because `ifconfig bridge create` autoloads themodule, but if we run the tests in a jail (e.g. because of kyua's upcomingexecenv.jail.params feature) we can't load the module and these tests can fail.Check if the module is loaded, skip the test if it is not.Reviewed by: markjMFC after: 1 weekEvent: Kitchener-Waterloo Hackathon 202406Differential Revision: https://reviews.freebsd.org/D45487(cherry picked from commit 480ad4055314efbfff7eedbb34272031d836ba89)
Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
pf tests: properly destroy renamed interfacesThe pfsync:pbr tests leaves lot of interfaces when they finish, makingother tests slower due to long time of loading scapy from pft_ping.pywhen more
pf tests: properly destroy renamed interfacesThe pfsync:pbr tests leaves lot of interfaces when they finish, makingother tests slower due to long time of loading scapy from pft_ping.pywhen more interfaces are present. When both sides of epair are assignedto jails, they are both removed from created_interfaces.lst and thuswon't be removed during cleanup from this file. An interface assigned tojail is stored in created_jails.lst but if it is renamed, it won't becleaned up either. Furthermore this test uses identical names formultiple interfaces across multiple jails which after destroying thosejails adds to overall confusion.To address this issue a new function is provided for renaming interfacesin jails and storing their new names in created_jails.lst for deletionduring cleanup.MFC after: 1 weekSponsored by: InnoGames GmbHDifferential Revision: https://reviews.freebsd.org/D38024
tests/divert: use PF_DIVERTNow all Python ports has been patched to support PF_DIVERT, andPython kinda promises to add support in 3.12 [1].This reverts commit 322b5b7c16666c40d2763f18c1a51e6f058
tests/divert: use PF_DIVERTNow all Python ports has been patched to support PF_DIVERT, andPython kinda promises to add support in 3.12 [1].This reverts commit 322b5b7c16666c40d2763f18c1a51e6f0580d4e9.[1] https://github.com/python/cpython/pull/96536#issuecomment-1303974686
tests: partial revert of 4627bc1e90fd17c8d4f44de6b932d456b67661fcPython's socketmodule isn't able to construct sockaddr when it doesn'trecognize the address family. Until this is solved in python
tests: partial revert of 4627bc1e90fd17c8d4f44de6b932d456b67661fcPython's socketmodule isn't able to construct sockaddr when it doesn'trecognize the address family. Until this is solved in python let thetests use the compatibility way to create divert(4) socket.
tests: use PF_DIVERT/SOCK_RAW instead of PF_INET/SOCK_RAW/IPPROTO_DIVERT
Reenable vnet tests in CIAfter restoring the associated commits the tests can be enabled again.This reverts commit 711524d961233cd017ee0fd17e4b87013720f1c8.This reverts commit c4585b938a04dfb157
Reenable vnet tests in CIAfter restoring the associated commits the tests can be enabled again.This reverts commit 711524d961233cd017ee0fd17e4b87013720f1c8.This reverts commit c4585b938a04dfb157d7a10fa958be13415145be.PR: 263767
tests: vnet tests started failing in CI, disable temporarilyAs a fallout of backing out 91f44749c6fe, vnet tests startedfailing in CI. Temporarily broadly disable vnet tests untilspecific cases
tests: vnet tests started failing in CI, disable temporarilyAs a fallout of backing out 91f44749c6fe, vnet tests startedfailing in CI. Temporarily broadly disable vnet tests untilspecific cases can be resolved, and file a bug.PR: 263767Differential Revision: https://reviews.freebsd.org/D35119Submitted by: kbowling
tests/net*: destroy interface from inside a jailThere is no guarentee that upon return of 'jail -r' all jail resourceswill be released. The test suite used to rely on that. Recent changesto the
tests/net*: destroy interface from inside a jailThere is no guarentee that upon return of 'jail -r' all jail resourceswill be released. The test suite used to rely on that. Recent changesto the PCB zones made jails delay releasing their resources, which endedwith interface leak in the test suite.Fix that by executing 'ifconfig foo0 destroy' inside the jail, insteadof doing 'jail -r' and expecting interfaces to pop up back immediatelyin the parent jail.Reviewed by: kpDifferential revision: https://reviews.freebsd.org/D33942
tests/divert: fix after 2ce85919bbba (IP source address validation)Just make the test packet more legitimate.Reviewed by: melifaro
pf tests: test ALTQ CBQ on top of if_vlanThe main purpose of this test is to verify that we can use ALTQ on topof if_vlan, but while we're here we also exercise the CBQ code. There'salready a bas
pf tests: test ALTQ CBQ on top of if_vlanThe main purpose of this test is to verify that we can use ALTQ on topof if_vlan, but while we're here we also exercise the CBQ code. There'salready a basis test for HFSC, so it makes sense to test anotheralgorithm while we test if_vlan.Reviewed by: donnerMFC after: 1 weekSponsored by: Rubicon Communications, LLC ("Netgate")Differential Revision: https://reviews.freebsd.org/D31649
tests: Only log critical errors from scapySince 2.4.5 scapy started issuing warnings about a few differentconfigurations during our tests. These are harmless, but they generatestderr output, whic
tests: Only log critical errors from scapySince 2.4.5 scapy started issuing warnings about a few differentconfigurations during our tests. These are harmless, but they generatestderr output, which upsets atf_check.Configure scapy to only log critical errors (and thus not warnings) tofix these tests.MFC after: 1 weekSponsored by: Rubicon Communications, LLC ("Netgate")
Add tests verifying IPv4/IPv6 output for TCP/UDP/raw paths.Reviewed by: kpMFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D24138
Add basic IPv4/IPv6 forwarding tests.MFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D24002
bridge: Basic test caseVery basic bridge test: Set up two jails and test that they can pass IPv4traffic over the bridge.Reviewed by: melifaro, philipSponsored by: The FreeBSD FoundationDiffere
bridge: Basic test caseVery basic bridge test: Set up two jails and test that they can pass IPv4traffic over the bridge.Reviewed by: melifaro, philipSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D23697
Add basic IPDIVERT tests.Reviewed by: lwhsu,kpDifferential Revision: https://reviews.freebsd.org/D23316
pkgbase: Put the sys/common test into the tests packageEvery other test is there so do the same for those.Reviewed by: bapt, gjbDifferential Revision: https://reviews.freebsd.org/D21504
tests: Move common (vnet) test functions into a common fileThe netipsec and pf tests have a number of common test functions. Theseused to be duplicated, but it makes more sense for them to re-use
tests: Move common (vnet) test functions into a common fileThe netipsec and pf tests have a number of common test functions. Theseused to be duplicated, but it makes more sense for them to re-use thecommon functions.PR: 236223