Hi Calvin, show us iptables -nL -t nat | grep NAT on the node with nova-network.
Could it be that your fixed_range flag in nova.conf covers both subnets, like 192.168.0.0/16 ? Second reason - I presume that the traffic from VM will go via your router if you access another VM via floating IP, so router should know the route to 192.168.0.x (static/ospf?) Regards, On Fri, Apr 20, 2012 at 7:03 AM, Calvin Walton <[email protected]>wrote: > Hi, > > I have instances running in Openstack using FlatDHCP networking mode. > Each one has an IP address in the internal subnet (192.168.22.x) and a > floating IP from the external subnet (192.168.0.x). > > I've found that from one instance, I cannot connect to another instance > (or, in fact, even the same instance) via the external floating address > (I have some monitoring tools that attempt to do this to verify that a > server is running). Connections from external computers work fine. > > My best guess is that there is an issue with the NAT on my nova-network > node not allowing loopback connections. Is this intentional, or a bug? > Is there a workaround available? > > For reference, I'm currently using OpenStack from the > 'latest-milestone-test' OpenStack PPA on Ubuntu 12.04 Precise. > > -- > Calvin Walton <[email protected]> > Blindside Networks http://www.blindsidenetworks.com/ > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -- Mike Scherbakov
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
