[
https://issues.apache.org/jira/browse/BROOKLYN-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117538#comment-14117538
]
ASF GitHub Bot commented on BROOKLYN-36:
----------------------------------------
Github user ahgittin commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/62#issuecomment-54076989
sounds like you're right, `iptables-save` is not very helpful here; instead
we need a
`alternatives(sudo("service iptables save"),
installPackage("iptables-persistent"))`
the commands above should be sufficient to have the iptables changes
persisted. i don't think we have a use case for a manual
`restoreIptablesRules`; but probably worth a comment in the text pointing at
this issue in case we need more functionality in future, or discover that our
thinking right now is wrong.
AFAIK we don't have any major use cases so would be good to do this small
change now, test it, and close this issue.
> 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.3.4#6332)
