cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilder Rodrigues (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8795) outgoing public traffic blocked in vm created using DefaultIsolatedNetworkOfferingWithSourceNatService
Date Thu, 24 Sep 2015 19:16:04 GMT

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

Wilder Rodrigues commented on CLOUDSTACK-8795:
----------------------------------------------

[~jayapal]

that fixed for VR, not for VPC VRs... but we will work on that,

Thanks!

Cheers,
Wilder

> outgoing public traffic blocked in vm created using DefaultIsolatedNetworkOfferingWithSourceNatService

> -------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8795
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8795
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.6.0
>         Environment: Xenserver 6.5, advanced zone, CS 4.6.0
>            Reporter: Rajani Karuturi
>            Assignee: Wilder Rodrigues
>            Priority: Blocker
>
> in case of vm launched in vpc, outgoing public traffic worked (I was able to ping google.com)
> But, in case of default isolated network(DefaultIsolatedNetworkOfferingWithSourceNatService)
vm, outgoing public traffic was blocked even after adding egress rule.
> It only worked after running the following on isolated VR
> iptables -I FW_OUTBOUND -j FIREWALL_EGRESS_RULES
> This issue is observed while reviewing PR #765 https://github.com/apache/cloudstack/pull/765#issuecomment-136962555



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message