Jon, I was facing a similar problem, the only difference was I had 2 NICs. I've tried many things to figure out what was happening, but I found nothing. What I did to fix it was use multi_host[https://lists.launchpad.net/openstack/msg16656.html] set up, then all vms was able to access internet. I think a important information is the iptables NAT table. And I workaround that may be usefull is kill dnsmasq, as restart nova services.
I would like to know more about why this is happening. Why vms can resolve name but can't receive the packets back, is a iptable issue? a route issue? masquerade, or what? hope you can fix it On Thu, Sep 27, 2012 at 3:08 PM, Jon Thomas <[email protected]> wrote: > Hi, > > I have a control node running nova-network using FlatDHCPManager and a > compute node only running nova-compute. It's a single nic setup. I can > start VM's on the compute node and ssh/ping them from the control node. > I can also ping from vm to control node bridge ip and em1 device ip. > However, I cannot ping from the VM to outside internet ( although DNS > apparently works). I set em1 on both to promisc and have ip-forwarding > on. iptables seem to have the right entries. Any ideas? > > here's conf, iptables, etc: > > http://paste.openstack.org/show/21159/ > > thx > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -- guilherme \n \tab maluf _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
