bugzilla-daemon at netfilter.org
2017-Jul-08 13:56 UTC
[Bug 1161] New: The lock problem causes the iptables return with exit code 0 without adding my rules to kernel.
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>
bugzilla-daemon at netfilter.org
2017-Jul-09 04:58 UTC
[Bug 1161] The lock problem causes the iptables return with exit code 0 without adding my rules to kernel.
https://bugzilla.netfilter.org/show_bug.cgi?id=1161
Hamid Reza Hasani <hr.hasani at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hr.hasani at gmail.com
--
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/20170709/3b450a36/attachment.html>
bugzilla-daemon at netfilter.org
2017-Jul-09 14:26 UTC
[Bug 1161] The lock problem causes the iptables return with exit code 0 without adding rules!
https://bugzilla.netfilter.org/show_bug.cgi?id=1161
Hamid Reza Hasani <hr.hasani at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|The lock problem causes the |The lock problem causes the
|iptables return with exit |iptables return with exit
|code 0 without adding my |code 0 without adding
|rules to kernel. |rules!
--
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/20170709/036ffd71/attachment.html>
bugzilla-daemon at netfilter.org
2017-Jul-12 05:08 UTC
[Bug 1161] The lock problem causes the iptables exit with 0 without adding any rule!
https://bugzilla.netfilter.org/show_bug.cgi?id=1161
Hamid Reza Hasani <hr.hasani at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|The lock problem causes the |The lock problem causes the
|iptables return with exit |iptables exit with 0
|code 0 without adding |without adding any rule!
|rules! |
--
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/20170712/526c9a52/attachment.html>