cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Kumar Lakineni" <anilkumar459.lakin...@gmail.com>
Subject RE: Problem with virtual router
Date Tue, 30 Sep 2014 21:00:49 GMT
Hi Jose,

Change the DNS1 to 8.8.8.8 and Internal DNS1 to 192.168.238.1 or can give it
too 8.8.8.8
In the UI click on "Network" tab there we can see the "egress rules".

For clarification, when we are creating a zone Cloud-Stack itself provides a
CIDR which is used for creating first router and the VMs can get DHCP from
that CIDR range and DNS also from that CIDR not from the DNS which we have
given at the time of creating zone.

I'm talking on Advanced Zone point of view.

Regards,
Anil.

-----Original Message-----
From: José Egas López [mailto:joseegas@farmaenlace.com] 
Sent: Tuesday, September 30, 2014 10:10 PM
To: users@cloudstack.apache.org
Subject: Re: Problem with virtual router

Hi Anil, I understand "Egress Rules" are defined on Security Groups, but 
I'm not working with SG.
There is another place where I can define egress rules?

*
Regards,
José
*

El 30/09/2014 8:39, Anil Kumar Lakineni escribió:
> Hi,
>
> Did u written "Egress rules" to the network using for VMs.
>
> Regards,
> Anil.
>
> -----Original Message-----
> From: José Egas López [mailto:joseegas@farmaenlace.com]
> Sent: Tuesday, September 30, 2014 5:37 PM
> To: users@cloudstack.apache.org
> Subject: Fwd: Problem with virtual router
>
> Does anybody knows about the problem below?
>
> -------------------------------------------------------
>
> Hi to all, I have a problem with my guest VMs; the virtual router VM is
> giving DHCP to guest VMs, the problem is that all VMs are viewing like a
> DNS Server to this virtual router, and are not viewing to the original
> DNS, so the guest VMs can not reach to the Internet.
> For example, I changed the configuration of my zone from this:
> DNS1: 8.8.8.8
> Internal DNS1: 192.168.238.1
>
> To this:
> DNS1: 192.168.238.1
> Internal DNS1: 192.168.238.2
>
> Where, in my example network 238.1 is the primary DNS and 238.2 the
> secondary.
> But the VMs still recognizing virtual router as the DNS.
> How can I fix it?
> Thanks!
>



---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com


Mime
View raw message