From: King, Michael (MKing@bridgew.edu)
Date: Tue Oct 02 2001 - 08:20:05 CDT
Personally, My students move so much, the subnet they register in, is not
the subnet they are in the following week.
I would find most usefull how many address, (leases) are currently active in
the given subnet. That was I know if I'm about to run out of address or
not.
-----Original Message-----
From: Peter Valian [mailto:valianp@southwestern.edu]
Sent: Monday, October 01, 2001 5:43 PM
To: netreg@southwestern.edu
Subject: Re: NetReg: Force use of DHCP server vs picking your own
manually
True. however, Im rethinking the usefulness of that overview. That
displays the subnet the user was on when they registered...not where
they are currently.
I don't know...would it be more or less useful to have the overview
display the current address allocation rather than where they registered
from?
thoughts?
-peter
King, Michael wrote:
>But if you do that, you run into the same problem I have.
>
>Doing this will "break" (term used very loosely here) Subnet overview.
>Subnet overview was built (I think) with the assumption that the
>Unregistered range would be in the same subnet as the Registered range.
>
>-----Original Message-----
>From: John Hascall [mailto:john@iastate.edu]
>Sent: Friday, September 28, 2001 9:40 AM
>To: netreg@southwestern.edu
>Subject: Re: NetReg: Force use of DHCP server vs picking your own
>manually
>
>
>
>>I think I get the idea now. I suppose ideally in addition to blocking
>>the non registered addresses, you'd keep the ip domain for registered
>>users with-in a few hundred addresses of your actual number of users to
>>maximize the chance that the dhcp server will try to use it. So you can
>>find out and yell at them.
>>
>
>>Further more, you could make your addressing system harder to figure out
>>by choosing more random smaller chunks of the address space in the
>>registered and unregistered pools. So, rather than 172.16.2.0-->
>>172.16.4.0 is unregistered and 172.16.5.0--> 172.16.8.0 being registered
>>addresses, something more like:
>>
>
> Actually using a non-routable (reserved for local LAN) address range
> for your unregistered users is best.
> For example:
>
> pool {
> range 10.11.20.1 10.11.20.199;
> allow unknown clients;
> deny dynamic bootp clients;
> min-lease-time 300;
> default-lease-time 600;
> max-lease-time 1200;
> option domain-name-servers netreg-1.ait.iastate.edu;
> }
>
> pool {
> range 129.186.21.1 129.186.21.199;
> deny unknown clients;
> deny dynamic bootp clients;
> ddns-updates on;
> }
>
> You will never route 10.x.y.z past your (campus) border router.
>
>John
>**********************************************************************
>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
>**********************************************************************
>
-- 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 ********************************************************************** ********************************************************************** 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