Actually the DHCP client on the box was setup during installation (pretty
much the default there). As for the server, that was done by installing
and enabling the server (via "yum install dhcpd" and "chkconfig ... dhcpd
on" and "/etc/init.d/dhcpd restart") with a hand edited /etc/dhcpd.conf
configuration file.
Basically the problem was that I unloaded the kernel module responsible
for the network interface on the DHCP server and then loaded a different
once and forgot to restart applicable services (DHCP) that bind direct to
devices - thus leading to no DHCP on the reloaded network interface for a
little over quarter of a day (until I restarted the DHCP server).
Obviously the server issue was an oops on my part, but the question is why
doesn't the client recover gracefully....
Cheers,
MaZe.
On Tue, 17 Jan 2006, Anthony Lordi wrote:
> Maciej. No answer to your loss of DHCP. Haven't even found the DHCP setup.
How did you set it up? Gui? Cli? I have CentOS 2.1, but imagine the same
setup. Have tried wired and wireless and have had no connection. Tony
On 1/17/06, Maciej ?enczykowski <maze@xxxxxxx> wrote:
>
> Hi,
>
> I've got a box with CentOS 4.2 x86_64 which had no DHCP access for a few
> hours, now I can't ping it (I'm pretty sure the box is still up). I
> expect the DHCP lease has timed out and the box has lost it's IP, I was
> expecting it to reacquire it once the DHCP came back up (configuration
> problem) - but no luck. Is this a known problem? Any solution/workaround?
> (for now or for the future...)
>
> Cheers,
> MaZe.
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
