From: Todd K. Watson (tkw@southwestern.edu)
Date: Fri Sep 22 2000 - 12:44:09 CDT
To Chris,
Thanks VERY much for sharing all you've done -- quite impressive!
To everyone on the list,
This is exactly what Peter and I would like to see from everyone that
has done any hacking on NetReg (most everyone who uses it). Many of
these tools which do not require specific ties into other systems (which
will vary from site to site) would be perfect for inclusion into ver2.
Our main motivations for use of MySQL is:
1) it is free for educational use
2) the Perl has excellent hooks into it (using the DBI)
3) we are using it for other web tools here at SU.
Now, I realize that Berkeley-like Database Managers (such as GDBM) and
other SQL DB's have #'s 1 & 2 also. One of the great things about the
Perl DBI is that you can migrate from one DBD to another fairly
seamlessly. I think ver 2 should be written as best possible to allow
various DBD's to be used with minor code alteration. Personally I think
NetReg should be free of the "requirement" of a database for operation,
though I think there are a lot of features which could be added as a
result of including one. Perhaps we should progress to have a "core"
NetReg system which is modular enough to easily add functionality -- of
course, that was the original intent of NetReg :')
</my $0.02>
Todd
Chris Smith wrote:
>
> I may have mentioned some of this before, but for what it's worth, here
> are some of the features I needed to add to the beta netreg:
>
> 1. No use of tmp files (1.2 has this!)
> 2. Additional registration info tracking/searching: name, phone number,
> room number, building, optional ethernet Jack#
> 3. Form entry protection from malicious users
> 4. Historical tracking in gdbm databases added, searchable and hot-linked
> with regs/leases
> 5. Registration totals (1.2 has this!)
> 6. Real time port state link & octets (from mib-2) reporting
> 7. Ethernet vendor ID lookups
> 8. ping/traceroute/dns toolbox
> 9. All printfs changed to print
> 10. DHCPCODE Stats reporting on server manager page
> 11. Automated rogue detection (using a permanent pool address w/out lease)
> and correction (router arp cache poisoning)
> 12. Temporary pool addresses filtered out at router
>
> Then, when I deployed 1.2, I added:
>
> 1. Reports:
> Regs by Operating System
> Reg'ed Ethernet Cards
> Disabled Network Ports
> Rogues
> Dhcp log
> Registration Errors
> Duplicate Registrations
> Real-time DHCP message traffic graph (thanks to RIT)
>
> 2. Removed Subnet overview, which was redundant (c.f. findconf)
>
> 3. Final GUI modifications - screenshots can be viewed at
> http://www.smu.edu/smunet/netreg/
>
> I hope this helps generate some ideas as to what others might find useful.
>
> Let me put my two cents in for gdbm (which I know) rather than mySQL
> (which I don't).
>
> By the way, for non-netreg products from which to glean ideas, everyone
> should be sure to look at
>
> RIT:
> http://www.rit.edu/~mrcsys/dhcp/
> http://ritdhcp.rit.edu/main.html
>
> WVU:
> http://dione.csc.wvu.edu/~grove/ResNet/ (which uses mySQL)
>
> And, commercially, IPWorks has come out with a netreg clone called
> campusworks which they don't seem to advertise, and "lucent" has QIP
> Registration Manager, which doesn't quite cut the mustard.
>
> I tried not to be long-winded.
>
> On 21 Sep 00, at 10:44, Peter Valian wrote:
>
> > Hi all,
> >
> > I'm in the whiteboard stage of NetReg 2 and would like some input as to
> > what features need to be added or other improvements.
> >
> > So far I have this:
> >
> > - Static IP over DHCP Support: will provide the ability for admins to
> > specify an IP address for a particular MAC.
> >
> > - MAC/Lease Tracking: leases will be placed in MySQL database to
> > provide a history of which IPs a MAC had; also would like to keep a
> > "last seen" history...may need to so this with SNMP queries to a router.
> >
> > - File locking routines
> >
> > - More views: view an entire subnet (would show which IP's are static,
> > which are DHCP and what's available); demographics (?)
> >
> > - Web-based installer
> >
> > Any suggestions would be greatly appreciated. Also, if you would like
> > to include a module you have written that would be very great.
> >
> > Thanks,
> > Peter
> >
> > PS- mailing list archive is now online...available off the NetReg main
> > page.
> >
> > http://www.netreg.org/
> >
> > --
> > 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
> > **********************************************************************
> >
>
> J. Christian Smith E-MAIL:chris@smu.edu
> Sr. Network Engineer * Southern Methodist University * Dallas * Texas
> **********************************************************************
> 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
> **********************************************************************
--
Todd K. Watson
Senior System & Network Administrator
Southwestern University, Georgetown, TX
tkw@southwestern.edu || TEL:512.863.1508 || FAX:512.863.1605
**********************************************************************
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:34 CDT