From: Peter Valian (valianp@southwestern.edu)
Date: Fri Apr 26 2002 - 14:13:31 CDT
chris,
the main problem I see is you're putting your pool declarations outside
your subnet declarations.
I didn't know that was even legal syntax, let alone what the behavior
would be.
let me know if it works.
-p
Chris Fabri wrote:
> I'll give this a shot. I put the authoritative as part of the global
> config, but that shouldn't make a difference. chris
>
>
>
> Peter Valian wrote:
>
>>Chris...try this. I think your syntax is incorrect.
>>
>>shared-network "netreg_test_233" {
>> subnet 172.28.233.0 netmask 255.255.255.0 {
>> authoritative;
>> option routers 172.28.233.1;
>> # Known clients get this pool
>> pool {
>> option domain-name-servers 129.105.49.1, 165.124.49.21;
>> one-lease-per-client true;
>> max-lease-time 7200;
>> default-lease-time 7200;
>> range 129.105.233.100 129.105.233.250;
>> deny unknown clients;
>> }
>> }
>> subnet 172.28.233.0 netmask 255.255.255.0 {
>> authoritative;
>> option routers 172.28.233.1;
>> # Unknown clients get this pool
>> pool {
>> option domain-name-servers 129.105.49.1;
>> one-lease-per-client true;
>> max-lease-time 120;
>> default-lease-time 120;
>> range 172.28.233.100 172.28.233.250;
>> allow unknown clients;
>> }
>> }
>>}
>>
>>
>>
>>
>>Chris Fabri wrote:
>>
>>>Yeah no problem:
>>>
>>>shared-network netreg_test_233 {
>>> subnet 172.28.233.0 netmask 255.255.255.0 {
>>> option routers 172.28.233.1;
>>> }
>>> subnet 129.105.233.0 netmask 255.255.255.0 {
>>> option routers 129.105.233.1;
>>> }
>>># unknown clients get this pool.
>>> pool {
>>> option domain-name-servers 129.105.49.1;
>>> max-lease-time 120;
>>> default-lease-time 120;
>>> range 172.28.233.100 172.28.233.250;
>>> allow unknown clients;
>>> }
>>># known clients get this pool.
>>> pool {
>>> option domain-name-servers 129.105.49.1, 165.124.49.21;
>>> max-lease-time 7200;
>>> default-lease-time 7200;
>>> range 129.105.233.100 129.105.233.250;
>>> deny unknown clients;
>>> }
>>>}
>>>
>>>Apr 21 21:28:02 netreg dhcpd: [ID 702911 local5.info] DHCPREQUEST for 129.105.23
>>>3.149 from 00:01:e6:64:4f:7c via 129.105.233.1: lease 129.105.233.149 unavailabl
>>>e.
>>>Apr 21 21:28:02 netreg dhcpd: [ID 702911 local5.info] DHCPNAK on 129.105.233.149
>>> to 00:01:e6:64:4f:7c via 129.105.233.1
>>>
>>>
>>>
>>>This is repeated several times, until:
>>>
>>>
>>>Apr 21 21:43:03 netreg dhcpd: [ID 702911 local5.info] DHCPDISCOVER from 00:01:e6
>>>:64:4f:7c via 129.105.233.1
>>>Apr 21 21:43:04 netreg dhcpd: [ID 702911 local5.info] DHCPOFFER on 172.28.233.25
>>>0 to 00:01:e6:64:4f:7c (NPI644F7C) via 129.105.233.1
>>>
>>>The client is Windows2000. We have 172.28.233.0/24 set up as a secondary
>>>address on the router interface for 129.105.233.0/24. Thanks! chris
>>>
>>>
>>>Peter Valian wrote:
>>>
>>>
>>>>Chris,
>>>>
>>>>can we see your conf before and after and an snippet from your error
>>>>log? what OS is the client?
>>>>
>>>>thanks,
>>>>-peter
>>>>
>>>>Chris Fabri wrote:
>>>>
>>>>
>>>>>I'm having a strange problem that I'm fairly certain is due to
>>>>>DHCP, but haven't gotten much helpful info from that direction, so
>>>>>I"m inquiring here.
>>>>>
>>>>>I'm using netreg 1.2 with dhcpv3 (that's the latest non-test, from Oct 2).
>>>>>I've had a couple of clients, after registering with netreg, that
>>>>>can't renew their leases. dhcp gives a "lease unavailable" error
>>>>>and then NAKs the request. This happened the first time that these
>>>>>clients tried to renew. After about an hour of NAKs, the client does
>>>>>a new DHCPDISCOVER, at which point it's given a lease from the unknown
>>>>>client range. This means at some point the host declaration has been
>>>>>removed, and i know i didn't do it. :)
>>>>>
>>>>>So I'm trying to see if anybody else has seen this behavior (didn't
>>>>>see anything in the archives). According to the DHCP folks, this
>>>>>problem was fixed in DHCP3.0.1rc8, but there are other problems with
>>>>>it, so that's no good for a production system.
>>>>>
>>>>>And I"m using the refresh-dhcpdconf.pl contributed by Steve Hideg,
>>>>>which doesn't appear to have the capability of making this type
>>>>>of change.
>>>>>
>>>>>TIA. chris
>>>>
>>>>
>>>>
>>>>--
>>>>Peter Valian
>>>>Network & Systems Administrator
>>>>Southwestern University
>>>>Georgetown, Texas
>>>>512.863.1586 office
>>>>512.863.1605 fax
>>>>--
>>>>
>>>>**********************************************************************
>>>>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
>>>>**********************************************************************
>>>>
>>>
>>>
>>>
>>
>>
>>--
>>Peter Valian
>>Network & Systems Administrator
>>Southwestern University
>>Georgetown, Texas
>>512.863.1586 office
>>512.863.1605 fax
>>--
>>
>>**********************************************************************
>>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
>>**********************************************************************
>>
>
>
>
-- Peter Valian Network & Systems Administrator Southwestern University Georgetown, Texas 512.863.1586 office 512.863.1605 fax --********************************************************************** 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:37 CDT