It is thought to work that way. The VR acts as a DNS server and is not
passing along the DNS values to the clients, but rather, doing the DNS
lookups itself.
On Tue, Jul 23, 2013 at 9:44 AM, chenxi...@aquala-tech.com wrote:
Assuming that I have only one LAN that is being served by an NAT
Hi,
I have recently tested the Virtual Router as described on the following page:
http://opennebula.org/documentation:rel4.0:router
The problem with this Virtual Router is that it only delivers the correct
IP address and network mask to the guest VM, but failed to deliver the
correct gateway
Assuming that I have only one LAN that is being served by an NAT server.
All the VM's are within the sam LAN, so they need to connect to the
outside world through a gateway, which is not xxx.xxx.xxx.1.
With the following context, the Virtual Router VM only gets the correct
IP, but not the gateway
Hi,
Did you check the resources from this mail? The wiki contains a guide on
windows guest contextualization.
http://lists.opennebula.org/pipermail/users-opennebula.org/2013-July/023731.html
Regards
--
Join us at OpenNebulaConf2013 http://opennebulaconf.com in Berlin, 24-26
September, 2013
--
please can anyone tell me how to prepare window 7 image to work with
opennebula 4.0.1
i installed the windows and create vm but network not configured with an ip
from context variables . i need the scripts that run and configure the
network interfaces, the dns servers in windows image .
