From: John Crowley (jcrowley@wolf.smith.edu)
Date: Wed May 28 2003 - 12:00:47 CDT
Thanks for the response. Good recommendations too, I was being a bit lazy
with my test network setup, but I may not have remembered to think it
through for my production ones!
I took about ten machines and did some more testing. I began picking up
the 131.229.21.x IPs at the high end (250). I think the reason I wasn't
seeing the 21 range with my previous test may have been some kind of
caching on the clients I was repeatedly using to test the netreg setup
prior to me expanding it over the full /23 range (was using /24
previously).
Anyhow, I'm happy with how things are looking now. Thanks again.
jac
On Wed, 28 May 2003, Robert Lowe wrote:
>
>
> John Crowley wrote:
>
> A couple of things, John...
>
> > I have a subnet I am testing netreg on that is a /23 range. My subnet.dat
> > has this line:
> > 131.229.20.0/23:Test Network:200:131.229.20.0/26
>
> Since you have identified 200.131.229.20.0/26 as the space for unregistered
> clients, your range below should match that, otherwise the statistics
> produced for registered/unregistered clients will not be accurate. See below.
>
> > I have my DHCP (full settings below) setup to hand out in the ranges
> > 20.1-20.60 (for temps) and 20.61-21.250 for perm addresses.
>
> Make this 200.131.229.20.1-63 (whether you use the zero address is up to you)
> and 200.131.229.20.64-200.131.229.21.250.
>
> > In my test
> > bed I am noticing that DHCP is handing out temp addresses starting at
> > 20.60 and working down. However, in the perm range it is starting at
> > 20.254 instead of 21.250 as I would expect.
> >
> > I don't have the systems to put on the network to try and test a 200+
> > machine network to make sure DHCP will start handing out those 21.x
> > addresses. (if anyone knows of an easy way to simulate this, I'd love to
> > know!).
> >
> > Is DHCP going to go 20.254 and work down to 20.61 and THEN switch to
> > 21.250 and work down? Did I mess something up in my config I'm not
> > seeing?
>
> A simple way to test would be to set the range from 20.253-21.2 and test
> with a handful of hosts. I don't remember off-hand how dhcpd hands out
> addresses in ranges that cross /24 boundaries, but I'd guess your assumption
> is correct.
>
> -Robert
>
> > Thanks in advance for any advice and the sanity checking!
> >
> > dhcpd.conf settings:
> >
> > subnet 131.229.20.0 netmask 255.255.254.0 {
> > authoritive;
> > option subnet-mask 255.255.254.0;
> > option broadcast-address 131.229.20.255;
> > option domain-name-servers 131.229.64.2, 131.229.64.1;
> > pool {
> > range 131.229.20.1 131.229.20.60;
> > option domain-name-servers 131.229.64.28;
> > option routers 131.229.21.254;
> > default-lease-time 120;
> > max-lease-time 120;
> > allow unknown clients;
> > }
> >
> > pool {
> > range 131.229.20.61 131.229.21.250;
> > option routers 131.229.21.254;
> > option domain-name-servers 131.229.64.2, 131.229.64.1;
> > default-lease-time 1209600;
> > max-lease-time 1209600;
> > deny unknown clients;
> > }
> > }
> >
> >
> >
> > jac
>
> **********************************************************************
> 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:39 CDT