brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-36) IptablesCommands.saveIptablesRules doesn't work as expected
Date Fri, 08 Aug 2014 14:06:19 GMT


ASF GitHub Bot commented on BROOKLYN-36:

Github user andreaturli commented on the pull request:
    @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](
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:
>             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,
for example

This message was sent by Atlassian JIRA

View raw message