Dear Sean, OpenNebula does not support Libvirt's NAT-network(192.168.122.0/24). You have to create a network environment as described here: http://opennebula.org/documentation:rel3.4:plan#networking
How are your hosts connected to each other? Regards, Jaime On Fri, May 11, 2012 at 4:40 PM, Sean Abbott <[email protected]> wrote: > Hello, > > I have a setup intended for selenium grid. I'll have a bunch of > machines using the default NAT for internet access and a management > network for communication between each other. The template for these > VMs is: > > NIC=[ > MODEL=virtio, > NETWORK="natnet0", > NETWORK_UNAME=oneadmin ] > NIC=[ > MODEL=virtio, > NETWORK="fullbackend", > NETWORK_UNAME=oneadmin ] > > > That's all working. I need one VM to be able to communicate with the > outside world on a single port (4444). I've set up template as follows: > > NIC=[ > MODEL=virtio, > NETWORK="natnet0", > NETWORK_UNAME=oneadmin, > IP=192.168.122.100, > WHITE_PORTS_TCP=4444 ] > NIC=[ > MODEL=virtio, > NETWORK="fullbackend", > NETWORK_UNAME=oneadmin ] > > The resulting VM can still use the internet and it can still communicate > with the other VMs. I can communicate with it on port 4444 from the > host that it's on, but not from outside. > > Is this what WHITE_PORTS_TCP is intended for? Am I doing something wrong? > > Thanks! > > sean > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | [email protected] _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
