On Thu, May 26, 2005 at 06:20:31PM +0200, Geert Stappers wrote:
> On Wed, May 25, 2005 at 11:56:40PM +0200, Finn-Arne Johansen wrote:
> > Ragnar Wisloff wrote:
> ...
> > > this behaviour:
> > >
> > > lease 192.168.199.184 {
> > > hardware ethernet 00:50:8b:c9:38:ef;
> > > }
> > > lease 192.168.199.180 {
> > > hardware ethernet 00:50:8b:c9:38:ef;
> > > }
> > >
> > > I'm wondering if the symptom is seen on other systems. This particular
> > > school just had a reinstall to sarge, and the problems started then.
>
> Sarge, but is it with dhcpd or dhcp3-server?
Please tell which DHCP server is used.
> > > The problem is solvable, but I would like to hear if this is just a
> > > freak problem or one that can be reproduced.
> >
> > Im seeing this as well. They get one IP during PXEboot, and another when
> > the dhcp client asks for an IP.
>
> Sounds like a good explanation to me.
>
>
> > The fix is to bind the clients to fixed
> > IP's. SInce this is a good thing anyway, this is just another way of
> > telling.
>
> Are you serious? Or just kidding?
>
> Should _each_ MAC address really get registered in the dhcpd.conf?
tjener:~
# grep recommend /etc/dhcp3/dhcpd.conf
# We still recommend defining fixed mac adress to ip adress mappings,
# We recommend defining fixed mac adress (a.k.a. hardware ethernet adress) to
tjener:~
#
> Cheers
> Geert Stappers
> Who sees DHCP as a releave for the system administrator.
Leaving this "challenge" for the thrid rainny day ...
Attachment:
signature.asc
Description: Digital signature