Re: dhcpcd wierdness
On Wed, 11 Nov 1998, Eric wrote:
> The network here at my school recently aquired a new T3 and a couple
> more subnets to go with it. Ever since then, dhcpcd refuses to
> function properly. Whenever I reboot, it fails to get me an IP (much
> less the same one which I had...which would be preferable). The only
> way I've found of getting an IP after a reboot is to go and run
> /etc/init.d/network (in the hopes that somehow this will influence
> dhcpcd to get my old IP), start and stop dhcpcd using
> /etc/init.d/dhcpc, then run /etc/init.d/network again (since
> restarting dhcpcd inevitably sets my IP to 0.0.0.0 again). I don't
> quite understand why this works...simply waiting for dhcpcd to get me
> an IP (which takes at least a couple hours...which is another thing I
> don't understand; I know that there are lots of IP's available) always
> ends in me getting a different IP than I previously had...which isn't
> good because then I have to go update my monolith domain name. Anyone
> know why dhcpcd just stopped working?
>
> Thanks,
> Eric.
>
>
Disclaimer: I don't know what I'm talking about.
When my school first converted to ATM/switched ethernet we found some
glitchiness with DHCP on our Windows/Mac boxes. I know next to nothing
about networking, but it had something to do with the DHCP server not
getting the message that the machine's IP is free because of a
reboot/shutdown, and therefore wouldn't re-assign that number, even to the
same machine. I think that I vaguely remember that this confused the ATM
switch so a new number didn't get assigned either until the DHCP lease
expired.
Or something....
If this sounds like it may have any bearing on your problem, let me know
and I'll talk to our network guru to refresh my memory on the issue.
--
Kent West
kent.west@infotech.acu.edu
KC5ENO - Amateur Radio: When all else fails.
Linux - Finally! A real OS for the Intel PC!
Reply to: