[
https://issues.apache.org/jira/browse/BROOKLYN-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14090781#comment-14090781
]
ASF GitHub Bot commented on BROOKLYN-36:
----------------------------------------
Github user andreaturli commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/62#issuecomment-51606179
@aledsage you are right about the fact that `iptables-persistent` needs to
be called any time a new ruls is added.
Also, notice that for debian-derivatives there is no `service iptables save`
So in askUbuntu I found a good reference
[this](http://askubuntu.com/questions/119393/how-to-save-rules-of-the-iptables)
where iptables-persistent seems to be the easiest solution (instead of touching
`/etc/network/interfaces`)
For RHEL derivatives we could instead use `service iptables save`
With that in mind I think we need to add a `restoreIptablesRules` that
should work with `saveIptablesRules` to achieve the iptables rules persistency.
Wdyt @ahgittin and @aledsage ?
> IptablesCommands.saveIptablesRules doesn't work as expected
> -----------------------------------------------------------
>
> Key: BROOKLYN-36
> URL: https://issues.apache.org/jira/browse/BROOKLYN-36
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Andrea Turli
> Assignee: Andrea Turli
> Priority: Minor
> Fix For: 0.7.0-SNAPSHOT
>
>
> This needs to be revisited as the behavior is not as described at
> http://www.thomas-krenn.com/en/wiki/Saving_Iptables_Firewall_Rules_Permanently,
> for example
--
This message was sent by Atlassian JIRA
(v6.2#6252)
