Re: NM vs clock

[José Queiroz <zekkerj gmail com>]

Are you using VMware to host this VM??? There are various issues with
VMware and clock on Linux guests.

2010/1/25 Neal Becker <ndbecker2 gmail com>:
> I have a virtual machine running F12, setup to bring up eth0 at boot (nm
> controlled).
>
> It kept failing dhcp.
> Jan 25 04:32:14 localhost NetworkManager: <info>  DHCP: device eth0 state
> changed (null) -> preinit
> Jan 25 04:32:14 localhost dhclient[1310]: Listening on
> LPF/eth0/08:00:27:b5:b3:6f
> Jan 25 04:32:14 localhost dhclient[1310]: Sending on
> LPF/eth0/08:00:27:b5:b3:6f
> Jan 25 04:32:14 localhost dhclient[1310]: Sending on   Socket/fallback
> Jan 25 04:32:15 localhost dhclient[1310]: DHCPREQUEST on eth0 to
> 255.255.255.255 port 67
> Jan 25 04:32:15 localhost dhclient[1310]: DHCPNAK from 10.32.111.2
> Jan 25 04:32:15 localhost NetworkManager: <info>  DHCP: device eth0 state
> changed preinit -> expire
> Jan 25 04:32:15 localhost NetworkManager: <info>  DHCP: device eth0 state
> changed expire -> preinit
> Jan 25 04:32:15 localhost dhclient[1310]: DHCPDISCOVER on eth0 to
> 255.255.255.255 port 67 interval 5
> Jan 25 09:32:16 localhost ntpd[1380]: ntpd 4 2 4p8 1 1612-o Wed Dec  9
> 11:49:11 UTC 2009 (1)
> Jan 25 09:32:16 localhost ntpd[1381]: precision = 0.076 usec
> Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #0 wildcard,
> 0.0.0.0#123 Disabled
> Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #1 wildcard,
> ::#123 Disabled
> Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #2 lo, ::1#123
> Enabled
> Jan 25 09:32:16 localhost ntpd[1381]: Listening on interface #3 lo,
> 127.0.0.1#123 Enabled
> Jan 25 09:32:16 localhost ntpd[1381]: Listening on routing socket on fd #20
> for interface updates
> Jan 25 09:32:16 localhost ntpd[1381]: kernel time sync status 2040
> Jan 25 09:32:16 localhost ntpd[1381]: frequency initialized -68.076 PPM from
> /var/lib/ntp/drift
> Jan 25 09:32:17 localhost dhclient[1310]: No DHCPOFFERS received.
>
> Notice the clock changed from 04:00 to 09:00 when ntpd started.  Apparantly,
> confusion over the clock time.
>
> Fixing the clock time seems to have solved the problem.  I guess the time
> change made dhclient think it should have timed out?
>
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>