[
https://issues.apache.org/jira/browse/BROOKLYN-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064773#comment-14064773
]
ASF GitHub Bot commented on BROOKLYN-36:
----------------------------------------
Github user aledsage commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/62#issuecomment-49287829
@andreaturli can you test empirical that changes survive a reboot, when
using `service iptables save`.
Then I'd be happy to merge.
You could also consider writing a few sentences about using
`iptables-persistent` (borrowing from + referencing
http://www.thomas-krenn.com/en/wiki/Saving_Iptables_Firewall_Rules_Permanently),
and see if you can contribute that to improve the ubuntu community site docs:
https://help.ubuntu.com/community/IptablesHowTo#Solution_.233_iptables-persistent
That should also be a good way to get feedback as to whether you are right!
Note this will only work on Ubuntu version >= Lucid (i.e. >= 10.04).
> 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)
