Lucian - <div><br></div><div>Could you also paste your iptables nat rules to the question?</div><div><br></div><div>Usually, when I get into a funky network state like you are in, I bust out tcpdump and map out exactly how packets are getting moved from interface to interface. That usually gets to the problem quickly.</div>
<div><br></div><div>A<br><br><div class="gmail_quote">On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz <span dir="ltr"><<a href="mailto:lucianthomaz@hotmail.com">lucianthomaz@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">
<font face="Tahoma" color="#366092">Hi Vish,</font><div><font face="Tahoma" color="#366092">Thank you, it's really working, but I'm having another trouble yet.</font></div><div><font face="Tahoma" color="#366092"><br>
</font></div><div><font face="Tahoma" color="#366092">I'm having this trouble in the log of the machine from Dashboard:</font></div><div><font face="Tahoma" color="#366092"><br></font></div><div><font color="#366092">wget: can't connect to remote host (169.254.169.254): No route to host</font></div>
<div><font color="#366092"><br></font></div><div><font color="#366092">And there are some other thing weird, in the log I can see that the network is trying during a while get the private ip for the machine and sometime it works, but sometime the network can't take that and so it takes a public ip from dhcp. Do you know something about that?</font></div>
<div><font color="#366092"><br></font></div><div><pre><pre>Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 10.0.0.3...
Received DHCP NAK
Sending discover...
Sending select for 192.168.100.219...
Lease of 192.168.100.219 obtained, lease time 3600
starting DHCP forEthernet interface eth0 [ [1;32mOK [0;39m ]
cloud-setup: checking <a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>
wget: can't connect to remote host (169.254.169.254): No route to host
</pre></pre></div><div><font color="#366092"><br></font></div><div><span style="color:rgb(54,96,146);font-size:10pt">My question in lauchpad have all my configurations and log. The only thing that I added in the configurations diferent from launchpad was this two flags:</span></div>
<div><span style="color:rgb(54,96,146);font-size:10pt"><br></span></div><div><span style="color:rgb(54,96,146);font-size:10pt"><div>--cc_host=192.168.100.140</div><div>--routing_source_ip=192.168.100.140</div><div><br></div>
<div><br></div></span></div><div><a href="https://answers.launchpad.net/nova/+question/192153" target="_blank">https://answers.launchpad.net/nova/+question/192153</a>
</div><div><font color="#366092"><br></font></div><div><font face="Tahoma" color="#366092"><br></font><br><br><div><font face="Tahoma" color="#333399"><strong>Lucian Thomaz </strong></font></div><br><br><div><div class="im">
<div></div>> Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server<br></div>> From: <a href="mailto:vishvananda@gmail.com" target="_blank">vishvananda@gmail.com</a><br>> Date: Tue, 3 Apr 2012 11:16:04 -0700<br>
> CC: <a href="mailto:sleepsonthefloor@gmail.com" target="_blank">sleepsonthefloor@gmail.com</a>; <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>> To: <a href="mailto:lucianthomaz@hotmail.com" target="_blank">lucianthomaz@hotmail.com</a><div class="im">
<br>> <br>> It is working!<br>> <br>> You are in the bios screen, so you probably just need to wait (software mode booting can take a while)<br>> <br>> If the vm doesn't ever actually boot, you may be attempting to boot a non-bootable image.<br>
</div></div></div> </div></div>
</blockquote></div><br></div>