cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-1369) Ipv6 - In dual Stack network , guest VM does not have the Ipv6 address of the router programmed in /etc/resolv.conf for DNS resolution.
Date Thu, 21 Mar 2013 01:25:14 GMT

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

Sangeetha Hariharan closed CLOUDSTACK-1369.
-------------------------------------------


Closing this issue since we provide support for IPV6 External DNS entries to be programmed
at Zone level now. 

There is another issue cloudstack-1755 to track the issue where IPV6 External DNS entries
and IPV6 Router details are missing.
                
> Ipv6 - In dual Stack network , guest VM does not have the Ipv6 address of the router
programmed in /etc/resolv.conf for DNS resolution. 
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1369
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1369
>             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 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>             Fix For: 4.1.0
>
>
> Ipv6 - In dual Stack network , guest VM does not have the Ipv6 address of the router
programmed in /etc/resolv.conf for DNS resolution.
> Steps to reproduce the problem:
> Set up: Advanced Zone with rhel 6.3 KVM host.
> Create a shared network with dual stack (ipv4 and ipv6).
> Deploy Vm in this network.
> Notice that the Ipv6 address of the router is not programmed in /etc/resolv.conf
> sangeetha@ubuntu-123:~$ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 10.223.136.67
> nameserver 72.52.126.11
> nameserver 72.52.126.12
> search hello1361
> Router info:
> root@r-15-VM:~# ifconfig
> eth0      Link encap:Ethernet  HWaddr 06:b1:1e:00:00:17
>           inet addr:10.223.136.67  Bcast:10.223.136.127  Mask:255.255.255.192
>           inet6 addr: fe80::4b1:1eff:fe00:17/64 Scope:Link
>           inet6 addr: fc00:3:1361:0:4716:16a7:a336:2f89/64 Scope:Global
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:45 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4686 (4.5 KiB)  TX bytes:5638 (5.5 KiB)
> eth1      Link encap:Ethernet  HWaddr 0e:00:a9:fe:03:a6
>           inet addr:169.254.3.166  Bcast:169.254.255.255  Mask:255.255.0.0
>           inet6 addr: fe80::c00:a9ff:fefe:3a6/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:203 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:25294 (24.7 KiB)  TX bytes:22851 (22.3 KiB)
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:4 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:200 (200.0 B)  TX bytes:200 (200.0 B)

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

Mime
View raw message