RE: NetReg: DCHP Question

New Message Reply Date view Thread view Subject view Author view Attachment view

From: King, Michael (MKing@bridgew.edu)
Date: Fri May 23 2003 - 14:34:01 CDT


Notes as I find them

DDNS-update-style should be interim. Ad hoc is no longer "correct"

As for your questions:

ISC's DHCP server give an address based on the GIAddres. This is usually
the address of the router that forwarded the packet to the DHCP address.

You said the clients are pulling the 10.99.x.x address, but not the
10.98.x.x address. Are you sending requests from the .x.98.x.x network?

While your on the netreg box, goto the /var/log/ folder do a "tail -n 300
messages" and you should see the traffic happeneing between the DHCP server
and the clients. Very usefull
Add a -f to it, and you can watch it as it happens. Post some snippets
from that log, and I'm sure we can lick this problem.

-----Original Message-----
From: Lavengood, Michael [mailto:MLavengood@franklincollege.edu]
Sent: Friday, May 23, 2003 2:45 PM
To: netreg@southwestern.edu
Subject: RE: NetReg: DCHP Question

All right I'm going to answer the questions that everyone asked in one
email. The router are set you send DHCP request. They are also setup so
the gateways see each other. I have installed the CIDR patch. Am I right
in that the DHCP Server gives the client the IP based on the option-router
setting or some other means. It pulls the 10.99.x.x addresses and works but
not the 10.98.x.x addresses. I've tried to switch over to the
shared-network but not working either. I have included it as well. Thanks
for all the ideas and help.

Mike

max-lease-time 120;
default-lease-time 120;
allow bootp;
allow booting;
option domain-name "franklincollege.edu";
server-identifier netreg.franklincollege.edu;
ddns-update-style ad-hoc;
ddns-updates off;
omapi-port 7911;

shared-network "SN_102" {
   subnet 10.99.0.0 netmask 255.255.0.0 {
          option routers 10.2.1.1;
          authoritative;
          pool {
            option domain-name-servers 10.2.1.3;
            one-lease-per-client true;
            max-lease-time 120;
            default-lease-time 120;
            range 10.99.0.0 10.99.0.254;
            allow unknown clients;
          }
   }
   subnet 10.2.0.0 netmask 255.255.0.0 {
         # Known clients get this pool.
          option routers 10.2.1.1;
          authoritative;
          pool {
            option domain-name-servers 10.1.1.2;
            one-lease-per-client true;
            max-lease-time 28800;
            default-lease-time 28800;
            range 10.2.1.6 10.2.1.254;
            deny unknown clients;
          }
   }
}

shared-network "SN_103" {
    subnet 10.98.0.0 netmask 255.255.0.0 {
          authoritative;
          option routers 10.3.1.1;
          pool {
            option domain-name-servers 10.2.1.3;
            one-lease-per-client true;
            max-lease-time 120;
            default-lease-time 120;
            range 10.98.0.0 10.98.0.254;
            allow unknown clients;
          }
   }
   subnet 10.3.0.0 netmask 255.255.0.0 {
         # Known clients get this pool.
          option routers 10.3.1.1;
          authoritative;
          pool {
            option domain-name-servers 10.1.1.2;
            one-lease-per-client true;
            max-lease-time 28800;
            default-lease-time 28800;
            range 10.3.1.6 10.3.1.254;
            deny unknown clients;
          }
   }
}

-----Original Message-----
From: Steve Hideg [mailto:hideg@saintmarys.edu]
Sent: Friday, May 23, 2003 10:06 AM
To: netreg@southwestern.edu
Cc: Lavengood, Michael
Subject: Re: NetReg: DCHP Question

Are the routers on those subnets configured to send DHCP requests to
your netreg box?

At 8:40 AM -0500 5/23/03, Lavengood, Michael wrote:
We are currently running Netreg v1.3rc2 in a test environment with
only one subnet (10.2.0.0/16) and it is working great. We are having
a problem though trying to get DHCP to see more than one subnet. I
have read the FAQ's on <http://www.netreg.org>www.netreg.org and did
not find a very good example on how to do this (Probably missed it).
Below I have added our dhcpd.conf file as well as our subnet.dat
file. What we are trying to do is give the FYEC Dorm a bad range of
10.99.0.6 - 10.99.0.254 and a good range of 10.2.0.6 - 10.2.0.254.
Then get Dietz Dorm a bad range of 10.98.0.6-10.98.0.254 and a good
range of 10.3.0.6-10.3.0.254. We haven't been able to figure out how
to add the pools with the shared network. Any and all help will be
greatly appreciated.

Thanks,

Mike

Michael Lavengood
Network Security Administrator

<http://www.franklincollege.edu/>Franklin College
Information Technology Services
501 East Monroe Street
Franklin, Indiana 46131<mailto:mlavengood@franklincollege.edu>

mlavengood@franklincollege.edu
Phone: 317.738.8148
Fax: 317.738.8146

---------------------------------------------------
DHCPD.CONF (The commented lines at the bottom work with just the one
Dorm/Subnet)

max-lease-time 120;
default-lease-time 120;
allow bootp;
allow booting;
option domain-name "franklincollege.edu";
server-identifier netreg.franklincollege.edu;
ddns-update-style ad-hoc;
ddns-updates off;
omapi-port 7911;

shared-network campus {
     subnet 10.0.0.0 netmask 255.0.0.0 {
         authoritative;
         option subnet-mask 255.255.0.0;
         # Unknown clients get this pool.
         pool {
             option routers 10.99.1.1;
             option domain-name-servers 10.2.1.3;
             max-lease-time 120;
             default-lease-time 120;
             range 10.99.0.0 10.99.0.254;
             allow unknown clients;
         }
        # Known clients get this pool.
         pool {
             option routers 10.2.1.1;
             option domain-name-servers 10.1.1.2;
             max-lease-time 28800;
             default-lease-time 28800;
             range 10.2.1.6 10.2.1.254;
             deny unknown clients;
         }
         # Unknown clients get this pool
         pool {
             option routers 10.98.1.1;
             option domain-name-servers 10.2.1.3;
             max-lease-time 120;
             default-lease-time 120;
             range 10.98.0.0 10.98.0.254;
             allow unknown clients;
         }
         # Known clients get this pool.
         pool {
             option routers 10.3.1.1;
             option domain-name-servers 10.1.1.2;
             max-lease-time 28800;
             default-lease-time 28800;
             range 10.3.1.6 10.3.1.254;
             deny unknown clients;
         }
}
}

##subnet 10.0.0.0 netmask 255.0.0.0 {
## authoritative;
## option subnet-mask 255.255.0.0;
## option broadcast-address 10.0.0.255;
## # Unknown clients get this pool.
## pool {
## option routers 10.2.1.1;
## option domain-name-servers 10.2.1.3;
## max-lease-time 120;
## default-lease-time 120;
## range 10.99.0.0 10.99.0.254;
## allow unknown clients;
## }
## # Known clients get this pool.
## pool {
## option routers 10.2.1.1;
## option domain-name-servers 10.1.1.2;
## max-lease-time 28800;
## default-lease-time 28800;
## range 10.2.1.6 10.2.1.254;
## deny unknown clients;
## }
##}

#<BEGIN_STATIC>#

---------------------------------------------------

SUBNET.DAT

10.2.0.0/16: FYEC: 250: 10.99.0.0/16:
10.3.0.0/16: Dietz: 250: 10.98.0.0/16:

---------------------------------------------------

**********************************************************************
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
**********************************************************************


New Message Reply Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:39 CDT