openstack team mailing list archive

[Anthony Young <sleepsonthefloor@xxxxxxxxx>]

Lucian -

Could you also paste your iptables nat rules to the question?

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.

A

On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz <lucianthomaz@xxxxxxxxxxx>wrote:

>  Hi Vish,
> Thank you, it's really working, but I'm having another trouble yet.
>
> I'm having this trouble in the log of the machine from Dashboard:
>
> wget: can't connect to remote host (169.254.169.254): No route to host
>
> 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?
>
> 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 http://169.254.169.254/2009-04-04/meta-data/instance-id
> wget: can't connect to remote host (169.254.169.254): No route to host
>
>
> 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:
>
> --cc_host=192.168.100.140
> --routing_source_ip=192.168.100.140
>
>
> https://answers.launchpad.net/nova/+question/192153
>
>
>
>
> *Lucian Thomaz *
>
>
> > Subject: Re: [Openstack] Dashboard VNC Console failed to connect to
> server
> > From: vishvananda@xxxxxxxxx
> > Date: Tue, 3 Apr 2012 11:16:04 -0700
> > CC: sleepsonthefloor@xxxxxxxxx; openstack@xxxxxxxxxxxxxxxxxxx
> > To: lucianthomaz@xxxxxxxxxxx
>
> >
> > It is working!
> >
> > You are in the bios screen, so you probably just need to wait (software
> mode booting can take a while)
> >
> > If the vm doesn't ever actually boot, you may be attempting to boot a
> non-bootable image.
>