1 | $Id: INSTALL 419 2010-07-04 17:52:38Z kdeugau $
|
---|
2 |
|
---|
3 | Installing the IPDB
|
---|
4 | ===================
|
---|
5 |
|
---|
6 | 1) Untar in a convenient location. Note that all URLs referenced internally currently assume they will be
|
---|
7 | presented at http://host/ip/.
|
---|
8 |
|
---|
9 | 2) Edit cgi-bin/MyIPDB.pm: you need to set the database DSN and company info. You
|
---|
10 | should probably also set the syslog facility and default custid.
|
---|
11 |
|
---|
12 | 3) Edit cgi-bin/CustIDCK.pm as needed to validate customer IDs.
|
---|
13 |
|
---|
14 | 4) Create the database, and the inital tables using cgi-bin/ipdb.psql.
|
---|
15 |
|
---|
16 | 5) User lists can be maintained two basic ways:
|
---|
17 |
|
---|
18 | a) Use the built-in user manager to add and remove users. This requires mod_auth_pgsql, configured
|
---|
19 | with read/write access to the IPDB users table. A default user admin, password admin, is created in step 4 above
|
---|
20 | - make sure to create a new user as an admin, and remove the default user.
|
---|
21 |
|
---|
22 | b) Maintain an external .htpasswd file of your own, configured however you like. In this case the
|
---|
23 | access-pwd-update.pl script should edited to match the .htpasswd filename/path and should be called from cron to
|
---|
24 | make sure new users get added to the database, and old ones get deleted. This extra maintenance of user lists is
|
---|
25 | necessary to support the access controls, which are stored in the database.
|
---|
26 |
|
---|
27 | You will have to either temporarily create a user "admin", so that user can grant other users priviledges, or run
|
---|
28 | the following on the database:
|
---|
29 |
|
---|
30 | UPDATE users SET acl='bacdsA' WHERE username='newadminuser';
|
---|
31 |
|
---|
32 | Replace 'newadminuser' as appropriate.
|
---|
33 |
|
---|
34 | If you don't do this, nobody will be able to make any changes; access-pwd-update.pl only grants read access.
|
---|
35 |
|
---|
36 |
|
---|
37 | Basic installation should now be complete! Add your ARIN, RIPE, LACNIC, AfriNIC, or APNIC allocations and start
|
---|
38 | documenting your netblock usage.
|
---|
39 |
|
---|
40 | If you want to export rWHOIS data, see http://www.unixadmin.cc/rwhois/ for a place to start on setting up an
|
---|
41 | rWHOIS server. Note that db2rwhois.pl creates and maintains the net-<cidr> trees, all you have to do is
|
---|
42 | configure the daemon itself. Schedule runs of cgi-bin/extras/db2rwhois.pl followed by rwhois_indexer. You'll
|
---|
43 | need to fill in correct organization contact info in MyIPDB.pm.
|
---|