*** From dhcp-server -- To unsubscribe, see the end of this message. ***
In writing this message I discovered the answer to my own question,
but that led to another, so here is part of the original message and
then finally my new question:
I'm playing around with v3a990424 on rhl 5.2 (2.0.36).
I want things set up such that unknown clients are given a short lease
in the "private" 10.10.26.x range. Known clients will be given valid
information as to what subnet they are really on (149.159.26). No
problem - set up a group statement. While trying to obtain a lease
for an unknown client, according to the log files, the client and
server have their conversation and it looks normal. However, the 95
box says that it was unable to obtain a lease. The server has
recorded the lease in the dhcpd.leases file. On the flip side, if I
add a host statement for the client, everything works as expected and
the client is good to go.
I also have my production dhcp server running on this same subnet,
with no leases defined for this subnet. I see the following in it's
records.
Apr 30 14:19:17 ipip usr/sbin/dhcpd: no free leases on subnet 149.159.26.0
Would this second dhcp server be sending something back to my test 95
box saying "sorry - no leases" and the 95 box is just giving up? I
think I just answered my own question - I unplugged the production
dhcp server for a few seconds and now it works. So, this begs the
question - should this be happening? If the server doesn't have a
lease for the client, shouldn't it just ignore it rather than give
some kind of "deny boot" response?
p.s. Why do my posts to this list take HOURS to come through? I
often receive direct responses from Ted LONG before the cc-reply shows
up on the list.
_ . | Trust the computer industry to
|_) || [EMAIL PROTECTED] | shorten "Year 2000" to Y2k. It was
|_)||||_| | this kind of thinking that caused
Passauer_| Residence Computing | the problem in the first place.
I know there hav
_ . | Trust the computer industry to
|_) || [EMAIL PROTECTED] | shorten "Year 2000" to Y2k. It was
|_)||||_| | this kind of thinking that caused
Passauer_| Residence Computing | the problem in the first place.
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
