[Bug 1161] New: The lock problem causes the iptables return with exit code 0 without adding my rules to kernel.

[bugzilla-daemon at netfilter.org]

https://bugzilla.netfilter.org/show_bug.cgi?id=1161

            Bug ID: 1161
           Summary: The lock problem causes the iptables return with exit
                    code 0 without adding my rules to kernel.
           Product: iptables
           Version: unspecified
          Hardware: x86_64
                OS: Ubuntu
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: iptables
          Assignee: netfilter-buglog at lists.netfilter.org
          Reporter: hr.hasani at gmail.com

Hi there,
I'm using iptables 1.6.1 and I have a problem with it. When I use iptables in a
script to add some rules, it doesn't work some times.
This problem becomes more obvious when you have some services that will come up
during boot time simultaneously and want to add some iptables rules. In this
case some rules will not add correctly.

To have a good scenario for this bug, you can use some services that have up
script and in their script they use iptables to add some firewall rules(e.g.
coova-chilli).
To view the bug run the following commands:
sudo service chilli stop; sudo service chilli start;sudo iptables -nvL ; sudo
iptables -F

if anything works fine, in each run you should see the INPUT and FORWARD chains
rules. But after some runs the chains will be clean or some rules are added and
other rules not!
I use -w and -W, but it doesn't work!

Thanks
Hamid Reza Hasani

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20170708/3c4d3a97/attachment.html>