firewall: count rules per chain and family, fix wrong order of ip6tables rules when ipv4 only or dual family rules are defined
SVN-Revision: 21533
This commit is contained in:
parent
f3bce8f0db
commit
409edb1b8e
1 changed files with 4 additions and 4 deletions
|
@ -47,11 +47,11 @@ fw_load_rule() {
|
|||
target=zone_${rule_dest}_${target}
|
||||
}
|
||||
|
||||
local rule_pos
|
||||
eval 'rule_pos=$((++FW__RULE_COUNT_'$chain'))'
|
||||
|
||||
local mode=$(fw_get_family_mode ${rule_family:-x} $rule_src I)
|
||||
|
||||
local rule_pos
|
||||
eval 'rule_pos=$((++FW__RULE_COUNT_'$mode'_'$chain'))'
|
||||
|
||||
[ "$rule_proto" == "tcpudp" ] && rule_proto="tcp udp"
|
||||
for rule_proto in $rule_proto; do
|
||||
fw add $mode f $chain $target $rule_pos { $rule_src_ip $rule_dest_ip } { \
|
||||
|
|
Loading…
Reference in a new issue