You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/01/01 00:05:50 UTC

[jira] [Commented] (CLOUDSTACK-5697) multiple public ranges don't work with vxlan on KVM

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

ASF subversion and git services commented on CLOUDSTACK-5697:
-------------------------------------------------------------

Commit 83f1f68408b3b9da9eac096d95638ee13aabab30 in branch refs/heads/4.3 from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=83f1f68 ]

CLOUDSTACK-5697 - public ip ranges should allow VNI rather than only working with untagged


> multiple public ranges don't work with vxlan on KVM
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-5697
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5697
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.3.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.3.0
>
>
> You can add multiple VLAN/VNI network ranges to your public traffic in cloudstack, these don't work with VXLAN on KVM. In other words, only guest traffic type creates VNI interfaces and bridges. Tested a solution and will push shortly.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)