From: Robert Lowe (robert.h.lowe@lawrence.edu)
Date: Fri Aug 30 2002 - 11:11:58 CDT
Rebecca Irvin wrote:
Rebeca,
Check the archives for messages announcing the CIDR kit; there will be
notes explaining the changes in detail. The kit will replace register.cgi,
admin.cgi, variables.pl, add subnet.pl and change subnet.dat.
All you have to do for your remote network is specify an address range
within that subnet that can be covered by another a smaller subnet. All
subnets are written in CIDR notation. The sample subnet.dat file should
look like:
# Fields followed by colons:
# 1. Subnet/mask length for registered clients
# 2. Location of subnet
# 3. Total number of leases from the subnet for registered clients
# 4. Subnet/mask length for unregistered clients if different,
# otherwise blank. Note, if you do not specify a different
# "subnet" for unregistered clients, active leases for this
# subnet (#1 above) will be counted as belonging to unregistered
# clients. You should specify a range for unknown clients in
# your dhcpd.conf file that be covered a subnet, no matter how
# small and regardless of whether it overlaps with the subnet
# for registered clients. A trailing colon is optional.
#
# e.g.
# 10.0.64.0/20:Engineering:425::
# 10.0.96.0/24:Sales:25:192.168.0.0/24:
# 10.0.128.0/24:Building 52:127:10.0.128.192/26:
#
I would never leave the 4th field blank, and in an upcoming new release
of this, it may not be, since not adding this will break some things in
the GUI.
If you are using overlapping subnets (as you intend to do), the key is
to set aside a range that is covered completely by a smaller subnet.
If you have trouble, let me know.
-Robert
> Thanks Mike,
>
> Do you know if there is any written documentation on this? I'm loathe to
> dive in to a new package with the students due any moment, but I may have
> no choice. I'd feel better if I could find a writeup on the new package :)
>
> Just to clarify my problem, in case anyone else sees something I don't,
> here's our problem.
>
> NAT was supposed to go into implementation this week, just before students
> came in. It hasn't gone smoothly, and I have to fall back to a fairly non
> existent fallback plan for the semester.
>
> I have 2 networks, a local and a remote. the local isn't a problem, works
> like a charm. They take temp IPs out of a secondary network, perms out of
> the primary. however, on our remote networks, we haven't been able to get
> the DHCP server to recognize a secondary network for our temp IPs, because
> it's too many hops. Now, I have enough IPs on the *remote* to put both the
> temp and perm IPs on the same network. However...I *dont* have enough IPs
> to do that on the main network.
>
> So, I'm stuck between a rock and a hard place, because I can't have
> students registering from both a 205.172. range, and a 192.168 address
> range according to the AllowableDomain declaration.
>
> *sigh*
>
> I love it when approval for equipment gets held up and things don't go in
> until the last minute...
>
> Any thoughts would be apreciated.
>
> Rebecca Irvin
> Lesley University
> Technical Opperations
>
> At 05:41 PM 8/29/02 -0400, you wrote:
> >You should investigate the Netreg-CIDR located in the contribs. It has this
> >functionality.
> >
> >Mike
> >
> >-----Original Message-----
> >From: Rebecca Irvin [mailto:rirvin@mail.lesley.edu]
> >Sent: Thursday, August 29, 2002 5:56 PM
> >To: netreg@southwestern.edu
> >Subject: NetReg: More than one Allowable Domain?
> >
> >
> >Has anyone come up with a way to allow more than one Domain to access the
> >registration interface?
> >
> >We'd like 2 separate networks to be able to register, with totally
> >different domains..
> >
> >Rebecca Irvin
> >Lesley University
> >Network Technitian
> >
> >**********************************************************************
> >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
> >**********************************************************************
>
> **********************************************************************
> 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:38 CDT