mirror of
https://gitlab.com/shorewall/code.git
synced 2025-02-23 05:01:34 +01:00
Apply patch from Tom 2005-06-15:
If the policy is QUEUE, and there is an entry in the BURST:LIMIT column for that policy then the BURST:LIMIT is not applied in some cases. The original evidence seems to have been removed from http://lists.shorewall.net/pipermail/shorewall-devel/2005-June/001206.html :-) git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2246 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
d31fd68261
commit
5fc89ede69
@ -7092,9 +7092,13 @@ apply_policy_rules() {
|
||||
;;
|
||||
esac
|
||||
|
||||
[ -n "$synparams" ] && \
|
||||
[ $policy = ACCEPT -o $policy = CONTINUE ] && \
|
||||
run_iptables -I $chain 2 -p tcp --syn -j @$chain
|
||||
if [ -n "$synparams" ]; then
|
||||
case $policy in
|
||||
ACCEPT|CONTINUE|QUEUE)
|
||||
run_iptables -I $chain 2 -p tcp --syn -j @$chain
|
||||
;;
|
||||
esac
|
||||
fi
|
||||
fi
|
||||
|
||||
done
|
||||
|
Loading…
Reference in New Issue
Block a user