Most forwarding tests invoke forwarding_enable() to enable the router and
forwarding_restore() to restore the original configuration. Add a helper,
adf_forwarding_enable(), which is like forwarding_enable(), but takes care
of scheduling the cleanup automatically.
Convert the tests that currently use defer to schedule the cleanup.
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/78b752c40069cde21c44dcf4c7b966a76a0eef2c.1758821127.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
h3=${NETIFS[p6]}
adf_vrf_prepare
-
- forwarding_enable
- defer forwarding_restore
+ adf_forwarding_enable
host_create "$h1" 192.0.2.1/28 2001:db8:1::1/64
host_create "$h2" 192.0.2.2/28 2001:db8:1::2/64
sysctl_restore net.ipv4.conf.all.forwarding
}
+adf_forwarding_enable()
+{
+ forwarding_enable
+ defer forwarding_restore
+}
+
declare -A MTU_ORIG
mtu_set()
{
h3=${NETIFS[p6]}
adf_vrf_prepare
-
- forwarding_enable
- defer forwarding_restore
+ adf_forwarding_enable
adf_ip_link_add "v1$h2" type veth peer name "v2$h2"
adf_ip_link_add "v1$h3" type veth peer name "v2$h3"
rp2=${NETIFS[p4]}
adf_vrf_prepare
-
- forwarding_enable
- defer forwarding_restore
+ adf_forwarding_enable
h1_create
switch_create