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

Sangeetha Hariharan commented on CLOUDSTACK-1461:
-------------------------------------------------

The behavior mentioned in the bug is the expected behavior.

We should NOT be programming the IPV6 entry of the non default router. Keeping 
this bug open to do these changes. 
                
> Ipv6 - From a Vm that that is part of 2 networks, Name resolution fails for 
> Vms that are part of non default network fails. 
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1461
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1461
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>
> Ipv6 - From a Vm that that is part of 2 networks, Name resolution fails for 
> Vms that are part of non default network fails
> Steps to reproduce the problem:
> Create a dual stack network ,N1
> Create a dual stack network, N2.
> Deploy a VM - vm1 in N1 and N2.
> Deploy a VM - vm2 in N2.
> From vm1 , try to reach vm2 using the vm-name.
> DNS name resolution fails.
> /etc/resolv.conf does not have the IPV4 address of the router that belongs to 
> non default networks.
> It does have the IPV6 address of the router that belongs to non default 
> networks.But seems like it is not being used for name resolution.
> 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.137.66
> nameserver fc00:3:1371::6a19:fed0:1932:3626
> nameserver fc00:3:1370::a659:ce38:85fe:a024
> search hello1371 hello1370
> sangeetha@ubuntu-123:~$
> sangeetha@ubuntu-123:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 06:7c:3c:00:00:4e
>           inet addr:10.223.137.71  Bcast:10.223.137.127  Mask:255.255.255.192
>           inet6 addr: fc00:3:1371:0:1111:3333:bbbb:ffff/64 Scope:Global
>           inet6 addr: fe80::47c:3cff:fe00:4e/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:556 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:331 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:49282 (49.2 KB)  TX bytes:33852 (33.8 KB)
> eth1      Link encap:Ethernet  HWaddr 06:22:cc:00:00:1d
>           inet addr:10.223.137.12  Bcast:10.223.137.31  Mask:255.255.255.224
>           inet6 addr: fc00:3:1370:0:81b8:c352:31e1:69e4/64 Scope:Global
>           inet6 addr: fe80::422:ccff:fe00:1d/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2003 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1634 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:188275 (188.2 KB)  TX bytes:223403 (223.4 KB)
> 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:18 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4038 (4.0 KB)  TX bytes:4038 (4.0 KB)
> sangeetha@ubuntu-123:~$

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

Reply via email to