Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for -w when iptables >= 1.4.20 #36

Merged
merged 2 commits into from
Nov 17, 2020

Conversation

AlexisEvo
Copy link
Contributor

When two instances of the iptables command are ran simultaneously they often encounter a race condition resulting in one of the commands not being executed. mutex_lock/unlock stops two instances of apf from colliding, but external programs that call iptables directly may result in apf not adding the necessary rules.

In 1.4.20, iptables added native support for locking, as well as a wait timeout flag:

http://git.netfilter.org/iptables/commit/?id=93587a04d0f2511e108bbc4d87a8b9d28a5c5dd8
http://git.netfilter.org/iptables/commit/?id=d7aeda5ed45ac7ca959f12180690caa371b5b14b

This PR adds the flag with a default timeout of 3 seconds when iptables is >= 1.4.20.

@rfxn rfxn merged commit 1aa47d2 into rfxn:master Nov 17, 2020
rfxn added a commit that referenced this pull request Nov 18, 2020
[New] add iptables locking support with iptables >= 1.4.20; pr #36
      IPT_LOCK_SUPPORT
      IPT_LOCK_TIMEOUT
[Fix] typos
rfxn added a commit that referenced this pull request Nov 18, 2020
[New] add iptables locking support with iptables >= 1.4.20; pr #36
      IPT_LOCK_SUPPORT
      IPT_LOCK_TIMEOUT
[Fix] typos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants