cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayapal Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-4613) security group rules issue in host
Date Thu, 12 Sep 2013 11:31:57 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765351#comment-13765351
] 

Jayapal Reddy edited comment on CLOUDSTACK-4613 at 9/12/13 11:31 AM:
---------------------------------------------------------------------

In KVM the iptables rules are organised differently. So this issue is not seen in kvm 
                
      was (Author: jayapal):
    In KVM the iptables rules are organised differently. So this issue is not seen in mvm
                  
> security group rules issue in host
> ----------------------------------
>
>                 Key: CLOUDSTACK-4613
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4613
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.1.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.2.1
>
>
> Observed the following security group iptables rules issues
> 1. iptables anti spoofing DROP rules add failed on VM reboot.
> inscmd = "iptables-save | grep '\-A " +  vmchain_default + "' | grep  physdev-in | grep
vif | sed -r 's/vif[0-9]+.0/" + vif + "/' | sed 's/-A/-I/'"
> Here the rules in inscmd are with out space for !--set, this causes rule execute failed.
> 2. The order of iptables rules are incorrect on VM reboot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message