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

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

Commit 823a7891e4b55dca2a241f8ee8ce846469cf5c4a in cloudstack's branch 
refs/heads/master from [~widodh]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=823a789 ]

CLOUDSTACK-10220: Configure IPv4 alias on VR regardless of IPv6 (#2396)

IPv4 and IPv6 are two different protocols and the presence of IPv6
in a network does not mean that IPv4 aliases/multiple subnets should
not be configured or supported by the VR.

This if-statement was written almost 5 years ago in a attempt to
add IPv6 support to CloudStack but was never fully implemented.

Signed-off-by: Wido den Hollander <w...@widodh.nl>

> IPv4 NIC alias is not added on Virtual Router in Basic Networking when NIC 
> has IPv6 address
> -------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10220
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10220
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server, Virtual Router
>    Affects Versions: 4.10.0.0
>         Environment: Basic Networking with IPv6 enabled
>            Reporter: Wido den Hollander
>            Assignee: Wido den Hollander
>              Labels: basic-networking, ipv6, virtual-router
>
> When multiple IPv4 subnets are configured inside a POD with Basic Networking 
> a NIC alias is created for the VR when a Instance starts and 
> DhcpAccrossMultipleSubnets is supported.
> However, when the Instance has a IPv6 address this IPv4 alias is not created 
> and prohibits the Instance from getting a IPv4 address



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to