<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You might try the following conf:<div><br></div><div>dmz_cidr=<your_floating_range></div><div><br></div><div>My guess is that traffic to other floating ips is getting snatted to the network host and lost in transit.</div><div><br></div><div>Vish</div><div><br><div><div>On Oct 25, 2012, at 7:27 AM, Christian Parpart <<a href="mailto:trapni@gmail.com">trapni@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hey all,<div><br></div><div>we're having quite a few compute nodes with Essex installed and one central nova-network gateway.</div><div><br></div><div>We now have a few floating IPs set up to route from the world through the gateway to these VMs.</div>
<div><br></div><div>However, accessing these floating (public) IPs from inside a <b>tenant's VM</b> results into timeouts,</div><div>but accessing the very same IP from a compute node (hypervisor) hosting those VMs actually does work.</div>
<div><br></div><div>Now I'm a bit confused, it seems like a routing issue or iptables NAT thing and would be really greatful</div><div>if anyone can help me out with a hint. :)</div><div><br></div><div>Is this known to not work or what do you need from me to actually understand my issue a bit more?</div>
<div><br></div><div>Many thanks in advance,</div><div>Christian Parpart.</div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></body></html>