Blame iptables/tests/shell/testcases/ip6tables/0004-return-codes_0

Packit Service d1fe03
#!/bin/sh
Packit Service d1fe03
Packit Service d1fe03
# make sure error return codes are as expected useful cases
Packit Service d1fe03
# (e.g. commands to check ruleset state)
Packit Service d1fe03
Packit Service d1fe03
global_rc=0
Packit Service d1fe03
Packit Service d1fe03
cmd() { # (rc, cmd, [args ...])
Packit Service d1fe03
	rc_exp=$1; shift
Packit Service d1fe03
Packit Service d1fe03
	$XT_MULTI "$@"
Packit Service d1fe03
	rc=$?
Packit Service d1fe03
Packit Service d1fe03
	[ $rc -eq $rc_exp ] || {
Packit Service d1fe03
		echo "---> expected $rc_exp, got $rc for command '$@'"
Packit Service d1fe03
		global_rc=1
Packit Service d1fe03
	}
Packit Service d1fe03
}
Packit Service d1fe03
Packit Service d1fe03
# test chain creation
Packit Service d1fe03
cmd 0 ip6tables -N foo
Packit Service d1fe03
cmd 1 ip6tables -N foo
Packit Service d1fe03
# iptables-nft allows this - bug or feature?
Packit Service d1fe03
#cmd 2 ip6tables -N "invalid name"
Packit Service d1fe03
Packit Service d1fe03
# test rule adding
Packit Service d1fe03
cmd 0 ip6tables -A INPUT -j ACCEPT
Packit Service d1fe03
cmd 1 ip6tables -A noexist -j ACCEPT
Packit Service d1fe03
Packit Service d1fe03
# test rule checking
Packit Service d1fe03
cmd 0 ip6tables -C INPUT -j ACCEPT
Packit Service d1fe03
cmd 1 ip6tables -C FORWARD -j ACCEPT
Packit Service d1fe03
cmd 1 ip6tables -C nonexist -j ACCEPT
Packit Service d1fe03
cmd 2 ip6tables -C INPUT -j foobar
Packit Service d1fe03
cmd 2 ip6tables -C INPUT -m foobar -j ACCEPT
Packit Service d1fe03
cmd 3 ip6tables -t foobar -C INPUT -j ACCEPT
Packit Service d1fe03
Packit Service d1fe03
exit $global_rc