Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 22 Jun 2013 07:32:19 +0000 (UTC)
From: "Prasanna Santhanam (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12654311.1371886293117.159925.1371886339945@arcas>
In-Reply-To: <JIRA.12654311.1371886293117@arcas>
References: <JIRA.12654311.1371886293117@arcas>
Subject: [jira] [Created] (CLOUDSTACK-3131) Unblock IGMP packets by security
 group rules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Prasanna Santhanam created CLOUDSTACK-3131:
----------------------------------------------

             Summary: Unblock IGMP packets by security group rules
                 Key: CLOUDSTACK-3131
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3131
             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, 4.0.2, 4.0.1, 4.0.0, 4.1.1, 4.2.0
            Reporter: Prasanna Santhanam
             Fix For: Future


From: Kenneth Warren <kwarren@orbistechnologies.com>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>
Subject: Security Groups and IGMP

Good Afternoon!

We are working with multicast and IGMP groups on our CloudStack infrastructure, and I have a question regarding security groups.

To create an ingress rule, one must navigate to the security groups panel then add a new rule based on protocol. The values allowed are ICMP, TCP, and UDP. I am concerned that the IGMP member query messages on the network are being
+blocked by the security group settings, as our VMs continually act as if they have been kicked out of the membership group.

Are IGMP packets blocked by security groups by default? If so, how do we enable them?

Thanks!


Full thread @ http://cloudstack.markmail.org/thread/ur4hzotraq3azmtz

--
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