<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; "><br><div><div>On Nov 21, 2012, at 8:10 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>I am having a rather serious with the central (OpenStack' Essex) nova-network gateway we have set up.</div><div>We have quite some floating IPs assigned to a few virtual machines, and it just works.</div>
<div>But since a few days (or weeks) I notice that some VM does not get inbound traffic from</div><div>external IPs, such as the internet, through the floating IP to be DNAT'ed to the application VM.</div><div><br></div>
<div>We tried to debug it, and it is definitely something with nova-network service going wrong here.</div><div><br></div><div><font color="#ff0000" style="background-color:rgb(255,255,255)">Now, a `pkill dnsmasq && sleep 2 && initctl restart nova-network` actually fixes it.</font></div></blockquote></div><div><blockquote type="cite">
<div><br></div><div>The question now is *why* does it fix it. The routing tables do not really seem to have changed,</div><div>unless I was missing something while checking :).</div><div><br></div><div>Is there anything nova-network is doing as well except setting up IPs and iptables?</div>
<div>Or - what is nova-network actually doing in general and what could be the reason the run into</div><div>such a situation.</div></blockquote><div><br></div>restarting nova-network will rebind all of the ips, restart dnsmasq and set up all of the iptables rules, so</div><div>it sounds like either the ip bindings were lost or the iptables rules or routes were somehow messed up. Nova-network</div><div>doesn't do anything special except configure bridges ips and iptables.</div><div><br></div><div>Vish</div><br></body></html>