What IP range are you running on your laptop and what is the default gateway on that network? Please tell me its 192.168.1.0 and 192.168.1.1???
Yes...it is 192.168.1.1/0. This is config is actually running on 2 different machines. I have control over the static ipaddresses.
I'm not that familiar with the templates you're using... .but it sounds like you might have a firewall issue. Either on the virtual box machines themselves or the VM guests.
On the VM guests do
service iptables status
make sure its stopped.
Thank you... Use Cases I am trying to achieve:
1) External clients outside of dom0 should be able to talk to the domU managed virtual machines. (The VBoxes are bridged now)
2) domU virtual machines should be able to talk to the internet
The "real" issue is that my domU guests need to go through the dom0 interface via the bridge defined in OVM Manager networking.
With all of the workflow changes in the product it is very difficult to see what needs to be done to accomplish the task as compared to OVM 2.* which was all driven by running scripts. These
changes plus the noise surrounding the related xen discussions on the internet makes it very difficult to get the issue sorted out. I have updated the link above with some additional screen shots.
I have looked at changing to NAT on dom0 and then port forwarding via iptables to the internet ..is this the correct method? I am just not really clear.
If you are installing Oracle VM Server on Oracle VM VirtualBox and you want to create a VM (domainU) with Oracle VM Server and to connect with this VM to the world, this is not permitted and your VM (domainU) can't access to network, this is because using Oracle VM Server (hypervisor) on Oracle VM VirtualBox and not problem with the NAT, IP Address or default gateway.