From: Nick Ciesinski (ciesinskna26@mail.uww.edu)
Date: Sat Sep 01 2001 - 07:03:11 CDT
Peter,
I understand what that error means. Ad the error was correct,
the mac was in dhcpd.conf already.. But it was Student "A"'s mac, not
Student "B"'s.
Is it possible to get a peak at the new lease parser in 1.3? I would
like to fix this problem before it happens again.
Nick
-----Original Message-----
From: owner-netreg@southwestern.edu
[mailto:owner-netreg@southwestern.edu] On Behalf Of Peter Valian
Sent: Saturday, September 01, 2001 4:25 AM
To: netreg@southwestern.edu
Subject: Re: NetReg: dhcpd3.0rc11 + lease file parsing
Nick,
That error means that the MAC address already exists in the dhcpd.conf
file...not the leases file.
the dhcp server doesnt clear the old leases out for some reason (Ted
Lemon told me it cleans out the leases file "once in a while"). what
maybe happening is a potential bug in the way I wrote the 1.2 lease
parser. At the time I was not too concerned with having multiple
expired leases with the same IP in the leases file. I rewrote the
leases parser in 1.3 to build a hash keyed on the IP. Ted did also tell
me that the last one in the leases file is the most recent. So when the
hash gets built now, it is the last occurrence of the IP that NetReg
uses to verify MAC.
I am almost certain this is what is happening...netreg in your case is
finding the old lease and using that MAC to check against the conf file.
last call for bugs...I will release v1.3 by tuesday.
-p
Nick Ciesinski wrote:
>
> Our students are starting to register... and I noticed something very
> interesting and bad at the same time..
>
> Here is what happened.
>
> Student "A" registered just fine. Student "A"'s old non registered
lease
> stayed in the dhcpd.leases file.
>
> 5 hours later Student "B" went to register, gets the same
non-registered IP
> as Student "A". Student "B" puts his username/pass in and gets the
message
> that the computer had already been registered... Well when I looked
in the
> dhcpd.leases file Student "A"'s entry was still there, just
> expired. Student "A"'s entry happened to be first on the list so that
is
> why Student "B" got the message. I then re-started the dhcp server
> manually and then Student "A"'s entry went away. But what I can't
figure
> out is why it cleaned it out on that re-start. There had been over 50
> re-starts from the time Student "A" registered from Student "B".
>
> I have upgraded to rc12 in hopes that it solves this, but I am not
holding
> my breath. I think that in the register.cgi we may need to check to
see if
> the lease has expired.
>
> Am I correct on thinking that this should not be happening with the
> dhcpd.lease file???
>
> Thanks,
>
> Nick Ciesinski
>
> **********************************************************************
> To unsubscribe from this list, send an e-mail message to
> majordomo@southwestern.edu containing a single line with the words:
> unsubscribe netreg
> Send requests for assistance to: owner-netreg@southwestern.edu
> **********************************************************************
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:36 CDT