You might try the following conf: dmz_cidr=<your_floating_range> My guess is that traffic to other floating ips is getting snatted to the network host and lost in transit. Vish On Oct 25, 2012, at 7:27 AM, Christian Parpart <trapni at gmail.com> wrote: > Hey all, > > we're having quite a few compute nodes with Essex installed and one central nova-network gateway. > > We now have a few floating IPs set up to route from the world through the gateway to these VMs. > > However, accessing these floating (public) IPs from inside a tenant's VM results into timeouts, > but accessing the very same IP from a compute node (hypervisor) hosting those VMs actually does work. > > Now I'm a bit confused, it seems like a routing issue or iptables NAT thing and would be really greatful > if anyone can help me out with a hint. :) > > Is this known to not work or what do you need from me to actually understand my issue a bit more? > > Many thanks in advance, > Christian Parpart. > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121025/62c6b69a/attachment.html>