You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2014/03/14 21:38:42 UTC

[jira] [Created] (CLOUDSTACK-6241) Dnsmasq programming error when deploy IPv6 and IPv4 in one VM with IPv4 as default network

Sheng Yang created CLOUDSTACK-6241:
--------------------------------------

             Summary: Dnsmasq programming error when deploy IPv6 and IPv4 in one VM with IPv4 as default network
                 Key: CLOUDSTACK-6241
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6241
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Virtual Router
    Affects Versions: 4.2.0, 4.3.0, 4.4.0
            Reporter: Sheng Yang
            Assignee: Sheng Yang
            Priority: Critical
             Fix For: 4.2.1, 4.3.0, 4.4.0


If one VM is created with both IPv4 and IPv6 network, and use IPv4 network as default network, then the programming of IPv6 network would be wrong in the VR.
Deploying Vm with a multiple NIC's when mixing IPv4/IPv6 networks results in incorrect entries 
in /etc/dhcphosts.txt on VR's. As a consequence dnsmasq doesn't provide IPv6 addresses in that case.
Below is a content of /etc/dhcphosts.txt on one of the VR's after spinning 2 VM's. First one had a 3 NIC's - 
one of them IPv4. Second 2 NIC's - only IPv6. As You can see first entry in incorrectly formatted.
06:aa:38:05:48:2d,set:,,vm-test1,infinite 
id:00:03:00:01:06:d8:fa:05:48:31,[3ffe:a1ca:c10d:1:3333:3333:3333:3335],vm-test2,infinite

Create 3 shared networks - one ipv4 only and two ipv6 only
Deploy VM with two NIC's in two ipv6 networks above
Observe, that everything works as expected
Deploy VM with 3 NIC's in all of the above defined networks, first NIC in ipv4
network
Observe that NIC's in ipv6 networks didn't get IP@ assigned,
content of dhcphosts.txt on VR's serving ipv6 networks is incorrect.



--
This message was sent by Atlassian JIRA
(v6.2#6252)