文件列表:

ipplan (0, 2011-07-03)
ipplan\contrib (0, 2011-07-03)
ipplan\contrib\create-test-users.sh (571, 2005-02-27)
ipplan\contrib\process-exports.txt (385, 2007-01-16)
ipplan\contrib\bind9_zone.xsl (1816, 2009-02-23)
ipplan\contrib\process-exports.pl.rej (875, 2008-04-05)
ipplan\contrib\ipplan-poller.php (10110, 2009-02-23)
ipplan\contrib\process-exports.pl (1909, 2009-02-23)
ipplan\contrib\dumproute.sh (130, 2005-01-08)
ipplan\contrib\ipplan2pc.xsl (1835, 2008-12-16)
ipplan\contrib\bind9_revzone.xsl (1231, 2009-02-23)
ipplan\contrib\qipImport-public.pl (21644, 2008-04-05)
ipplan\contrib\isc_dhcp1.xsl (897, 2007-01-24)
ipplan\contrib\isc_dhcp2.xsl (1209, 2007-01-24)
ipplan\contrib\bind9_zone.xsl.rej (697, 2008-04-05)
ipplan\contrib\dumproute.txt (437, 2005-01-08)
ipplan\contrib\bind9_zone.dtd (736, 2005-01-08)
ipplan\class.dbflib.php (44887, 2011-07-03)
ipplan\INSTALL-WINDOWS (5424, 2011-07-03)
ipplan\templates (0, 2011-07-03)
ipplan\templates\display (0, 2011-07-03)
ipplan\templates\display\fwdzonetemplate.xml (240, 2006-07-03)
ipplan\templates\display\basetemplate.xml (240, 2006-07-03)
ipplan\templates\display\iptemplate.xml (251, 2008-12-30)
ipplan\templates\display\custtemplate-ripe.xml (761, 2006-07-03)
ipplan\templates\display\iptemplate.xml.sample (781, 2006-07-04)
ipplan\templates\display\basetemplate.xml.dhcp (1774, 2006-09-22)
ipplan\templates\display\custtemplate.xml (634, 2006-07-03)
ipplan\templates\display\basetemplate-dhcp.xml (1153, 2006-09-27)
ipplan\templates\swip_reassign-simple-remove3.0.xsl (751, 2005-01-08)
ipplan\templates\swip_reassign-simple-modify3.0.xsl (751, 2005-01-08)
ipplan\templates\ripe_person_simple-1.0.xsl (714, 2005-06-26)
ipplan\templates\swip_wdb1.4_modify.xsl (1337, 2005-01-08)
ipplan\templates\swip_wdb1.4_new.xsl (1337, 2005-01-08)
ipplan\templates\swip_wdb1.4_delete.xsl (1337, 2005-01-08)
ipplan\templates\ripe_assign-simple-1.0.xsl (706, 2005-06-24)
ipplan\templates\swip_reassign-simple-new3.0.xsl (751, 2008-12-19)
ipplan\messages.po (91243, 2011-07-03)
... ...

IPplan - IP address management and tracking Revision History Revision 4.81 2007-01-23 Revised by: re Revision 2.91 2002-05-17 Revised by: re IPplan is a free (GPL), web based, multilingual, IP address management and tracking tool written in [1]php 4, simplifying the administration of your IP address space. IPplan goes beyond IP address management including DNS administration, configuration file management, circuit management (customizable via templates) and storing of hardware information (customizable via templates). IPplan can handle a single network or cater for multiple networks and customers with overlapping address space. See the introduction section for more. _________________________________________________________________ Table of Contents 1. [2]Introduction 1.1. [3]Copyright Information 1.2. [4]Disclaimer 1.3. [5]New Versions 1.4. [6]Credits 1.5. [7]Feedback 1.6. [8]Translations 2. [9]Requirements 2.1. [10]Databases 2.2. [11]Additional features 3. [12]Installation 3.1. [13]Customization 4. [14]Downloads, bugs and forums 4.1. [15]Screenshots 5. [16]Mode of operation 5.1. [17]Services company 5.2. [18]ISP 6. [19]Concepts 6.1. [20]Deployment strategy 6.2. [21]Linking addresses 7. [22]Administration 7.1. [23]Admin user 7.2. [24]Customer access 7.3. [25]Subnet access 7.4. [26]Group authority boundaries 8. [27]Circuit administration, host configuration data and asset information 9. [28]Device configuration file management 10. [29]DNS administration 10.1. [30]Handling exported zones 10.2. [31]Automatic updating of zone records 11. [32]Dealing with registrars 12. [33]Searching 12.1. [34]Searching for individual address details 12.2. [35]Searching areas and ranges 13. [36]Config file 14. [37]Importing data 14.1. [38]TAB delimited data 14.2. [39]Importing using NMAP 15. [40]Templates 15.1. [41]Customer, Subnet, DNS and IP address templates 15.2. [42]Registrar templates 16. [43]DHCP 17. [44]Triggers 18. [45]External command line poller 19. [46]IP address request system 20. [47]Authentication schemes 21. [48]Problems 22. [49]Limitations 23. [50]Questions and Answers (FAQ) [51]http://sourceforge.net _________________________________________________________________ 1. Introduction IPplan is a web based, multilingual, IP address management and tracking tool based on [52]php 4, simplifying the administration of your IP address space. IPplan can handle a single network or cater for multiple networks with overlapping address space. Current functionality includes * internationalization * importing network definitions from routing tables * importing definitions from TAB delimited files and [53]NMAP's XML format * multiple administrators with different access profiles (per group, allowing access per customer, per network etc.) * define address space authority boundaries per group * finding free address space across a range * split and join networks to make them smaller and larger - ip definitions remain intact * display overlapping address space between networks * search capabilities * an audit log - contents before and after change is logged * statistics * keeping track of and sending SWIP/registrar information * DNS administration (forward and reverse zones, import existing zones via zone transfer) * template system to extend IPplan to contain site specific information like circuit data, host configuration data, asset information * device configuration file management * external stylesheet to change display look * triggers - every user event can call a user defined function - useful to execute backend DNS scripts * external poller - scan subnets for active addresses to gather usage statistics * IP address request system - allows users to request static IP addresses from the database Two authentication methods are available - either IPplan's own internal authentication scheme, or alternatively make use of any external Apache authentication module. This includes single sign on systems like SiteMinder or your own scheme based on LDAP, or any other Apache compatible system. _________________________________________________________________ 1.1. Copyright Information This document is copyrighted (c) 2002 Richard E and is distributed under the terms of the Linux Documentation Project (LDP) license, stated below. Unless otherwise stated, Linux HOWTO documents are copyrighted by their respective authors. Linux HOWTO documents may be reproduced and distributed in whole or in part, in any medium physical or electronic, as long as this copyright notice is retained on all copies. Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions. All translations, derivative works, or aggregate works incorporating any Linux HOWTO documents must be covered under this copyright notice. That is, you may not produce a derivative work from a HOWTO and impose additional restrictions on its distribution. Exceptions to these rules may be granted under certain conditions; please contact the Linux HOWTO coordinator at the address given below. _________________________________________________________________ 1.2. Disclaimer No liability for the contents of this documents can be accepted. Use the concepts, examples and other content at your own risk. As this is a new edition of this document, there may be errors and inaccuracies, that may of course be damaging to your system. Proceed with caution, and although this is highly unlikely, the author(s) do not take any responsibility for that. All copyrights are held by their by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements. Warning It is strongly recommended to make a backup of your system before major installation or upgrades and to backup at regular intervals. _________________________________________________________________ 1.3. New Versions See the CHANGELOG file for more information. _________________________________________________________________ 1.4. Credits Thanks to [54]ValueHunt Inc. for the use of their layout class used for rendering all HTML pages. Thanks to [55]AdoDB for the use of their generic database abstraction class. Thanks to [56]Vex for their Visual Editor for XML used to generate the IPplan documentation. Thanks to [57]The PHP Layers Menu System for their menu system. _________________________________________________________________ 1.5. Feedback Feedback is most certainly welcome for this document. Without your submissions and input, this document wouldn't exist. Please send your additions, comments and criticisms to the following email address : <[58]ipplan@gmail.com>. _________________________________________________________________ 1.6. Translations See the INSTALL and TRANSLATIONS files on how to enable multilingual support and how to do a translation to your own language. Doing a translation does not require any programming experience. Current languages supported are English, Bulgarian, French - Auto Translation, German - Auto Translation, Italian - Auto Translation, Norwegian - Auto Translation, Portuguese - Auto Translation and Spanish - Auto Translation. Nickola Kolev for the Bulgarian translation - nikky at mnet.bg. Conrado Pinto Rebessi for the Brazillian translation - conradopinto at yahoo.com.br Tadashi Jokagi for the Japanese transalation - elf2000 at users.sourceforge.net Vladimir Leshchenko for the Russian translation - worker at smtn.stavropol.ru _________________________________________________________________ 2. Requirements IPplan requires a working web server installation. Currently the [59]Apache web server is preferred, but php as an ISAPI or CGI module on IIS works too - follow the appropriate installation instructions in the IPplan directory (INSTALL-IIS+MSSQL). Apache works just fine on Windows platforms too. For installing Apache on a Windows platform, follow [60]these instructions. Or you can use [61]AppServ or [62]WampServer which are complete installation packages for Apache, MySQL and PHP for Windows - just add IPplan by following the installation instructions in the IPPLAN-WINDOWS file (part of IPPlan). _________________________________________________________________ 2.1. Databases IPplan requires a working database installation. The following databases currently work: * [63]MySQL 3.23.15 or higher (preferred) * [***]PostgreSQL 7.1 or higher * [65]Oracle 9i or higher (SQL99) * Microsoft SQL server (both 7 and 2000) The following may work, but are untested - Sybase. In fact, any database that supports SQL99 compliant joins, in particular LEFT JOIN, should work. See limitations section below for more. The web scripting language [66]php 4.1 or higher must also be installed as a module in Apache (NOT as a cgi). Php must have the preferred database driver compiled in and enabled. See the respective web sites and installation documents for more detail. IPplan works just fine with a combination of the Apache web server and php on a Windows platform - just read the relevant installation instructions for Windows carefully. Tip IPplan is also known to work in a distributed, replicated MySQL environment with multiple database servers. See [67]www.oreilly.com for more information. _________________________________________________________________ 2.2. Additional features To enable SNMP support, you will require the [68]ucd-snmp package installed and configured in your environment. This must also be activated in the php configuration. SNMP support is only required if you wish to read routing tables directly from routers. _________________________________________________________________ 3. Installation Follow the instructions for your platform and database in the INSTALL files in the IPplan directory. _________________________________________________________________ 3.1. Customization IPplan is customizable in many ways. See the sections on templates, triggers and pollers. You can also extend the menu system to include your own custom menus for other systems at your site - see the config.php file for an example. _________________________________________________________________ 4. Downloads, bugs and forums You can report bugs, contribute to forums and download it [69]here and look at the latest [70]TODO and [71]CHANGELOG. _________________________________________________________________ 4.1. Screenshots You can find some screen shots [72]here. _________________________________________________________________ 5. Mode of operation There are two modes of operation, one can be classified as a services company and the other as an ISP. _________________________________________________________________ 5.1. Services company As a services company your primary use of IPplan will be to manage individual IP address records and the address plan of one or more customers. _________________________________________________________________ 5.2. ISP In ISP mode, you will assign blocks of IP address space to your customers. In this mode, you will not be concerned at all with individual IP address records and how the customer breaks down his assigned address space. When you operate as an ISP, you may also generate SWIP/registrar entries, which are only useful if you deal directly with ARIN or any other registrar. (SWIP is enabled in the config.php file, see ARIN [73]tutorial for more details). All the relevant SWIP/registrar information is entered when the customer is created. When using this mode, I suggest creating a dummy customer which holds all the allocated address space from your regional registrar (ARIN?) already broken up into the various blocks that you will eventually assign to your customers. All these blocks should be called "free" to allow them to be found using the "Find free" menu option. Once you are ready to assign a block, create a new customer with all the relevant SWIP/registrar information completed, go to your dummy customer and move a block of address space to the newly created customer, and finally generate a SWIP/registrar entry for the new block. In this mode areas and ranges are not too relevant except for the dummy customer (see concepts below). You may also need to create a template for your registrar in the templates directory. If you have done this, feel free to contribute it to IPplan. _________________________________________________________________ 6. Concepts The flow of address management is based on the creation of areas, then ranges which belong to areas, and finally, subnets which belong to ranges. Actually, only subnets are required, but on large networks it makes logical sense to group the network into areas to ease administration and to reduce routing updates on the network. There is a jpeg drawing included with the distribution that graphically shows these relationships. The methodology employed borrows significantly from OSPF routing concepts which are explained more fully [74]here. _________________________________________________________________ 6.1. Deployment strategy So in a new installation, first create the areas, then create ranges adding them to areas, and finally create subnets. Searching is now a simple matter of selecting an area which will display all the ranges for the area, or selecting no area and simply selecting a range from the total list of ranges, or simply selecting a base network address. Note Within a customer or autonomous system, no overlaps of address space is allowed. This follows standard IP addressing rules. You can have overlapping ranges/aggregates, but the default behaviour of ranges also prevents overlaps. This can be changed in the config.php file. To handle challenges like NAT or other overlapping address space, you will be required to create multiple autonomous systems. See 'Searching' below how to see information across multiple autonomous systems. _________________________________________________________________ 6.2. Linking addresses IP address records can be linked together. This allows one address or multiple addresses to reference another address or addresses. Using this feature allows for the referencing of NATed addresses or having a link to a loopback address of a device. Linking is done on the IP address details page by completing the "Linked address" field. Once the field is completed, you can follow the link. The link also appears on subnet summary pages. You can also link many addresses in one go by choosing multiple addresses in the "Select multiple addresses to do a bulk change" window, then completing the "User" field as follows: LNKx.x.x.x userinfo The LNK identifier must be in uppercase, followed by exactly one valid IP address with no spaces, then followed by an optional space and user description. After the page is submitted, the embedded LNK will vanish. Note If the destination record of a linked address does not exist, a record will automatically get created pointing back to the source address, but only if the destination subnet exists. This is to signal the "Find Next Free" address logic of the subnet that the destination address is used. _________________________________________________________________ 7. Administration The access control is divided up into three layers and revolves around the creation of groups: _________________________________________________________________ 7.1. Admin user Firstly you will need to create users and groups using the admin user defined in the config.php script. The admin user can only be used on the admin pages. Once you are done with the admin functions, you will be required to re-authenticate as one of the newly created users as soon as you access functions on the main index page. _________________________________________________________________ 7.2. Customer access When a customer is created, a group must be assigned to the customer. This will be the customers admin group and all members of this group can create and delete both subnets, ranges, areas and individual IP address records for the customer. When the subnet is created, the creator will choose a subnet admin group. _________________________________________________________________ 7.3. Subnet access The users assigned to the group that has subnet access can only modify individual IP records for that subnet. Initially I would create three groups, one group that can create customers, one group that can create subnets, areas and ranges, and another group which can only modify individual IP records. Normally in large networks the people that modify IP records are not the same people that administer routers and configure the IP address space. If a group is set to see only a particular customer, the same group needs to be used for all operations for the customer. The side effect to this is that the users assigned to the group have full access to the customer and can make any changes to the customers data, including creating and deletion of subnets. This is not ideal and will be changed in future. Tip Groups can be created that prevent certain users from changing an administrator defined number of reserved addresses at the start of a subnet. _________________________________________________________________ 7.4. Group authority boundaries Areas of responsibility can be assigned to a group, thus limiting what address space a group can create networks in. The default behavior allows administration anywhere. Care should be taken when using this feature as changing the boundaries at a later stage may orphan some parts of the database and yield data inaccessible. Note If a user belongs to multiple groups and one of the groups does not have boundaries defined, then the user is granted all access. Thus boundaries are a sum of all the boundaries the user belongs to. Tip Bounds are also useful to create users that only have read access to the IPplan information. Select the "Read Only" option when creating a new group. _________________________________________________________________ 8. Circuit administration, host conf ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：