You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/02/27 04:48:14 UTC

[jira] [Resolved] (CLOUDSTACK-1232) Ipv6 - Guest Vms are not able to get Ipaddress when executing dhclient command when using "/96" network.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang resolved CLOUDSTACK-1232.
------------------------------------

    Resolution: Fixed
    
> Ipv6 - Guest Vms are not able to get Ipaddress when executing dhclient command when using "/96" network.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1232
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1232
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>         Environment: Latest build from network refactor branch.
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>             Fix For: 4.1.0
>
>
> Steps to reproduce the problem:
> Create a IPV6 network using “/96” CIDR.
> Deploy a Vm in this network.
> Router assigns an Ipaddress to this VM.
> root@r-51-VM:~# cat  /etc/dhcphosts.txt
> id:00:03:00:01:06:ce:88:00:00:3c,[fc00:3:1380::9fe5:5d25],vm-1380-1,infinite
> But  guest Vms are not able to get the ipaddress.
> I see the following in the router logs when , dhclient request is made from the guest.
> Feb 12 02:31:21 dnsmasq-dhcp[1805]: no address range available for DHCPv6 request via eth0
> Feb 12 02:31:22 dnsmasq-dhcp[1805]: no address range available for DHCPv6 request via eth0
> Feb 12 02:31:24 dnsmasq-dhcp[1805]: no address range available for DHCPv6 request via eth0

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