- db-wg - mailman.ripe.net

Re: IP Address Management Tool
by Tobias Cremer 30 Jan '07

30 Jan '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Berthy, On 29.01.2007 15:04, berthy.vanderjagt(a)kpn.com wrote: > And has anyone good recommendations for an IP Management tool to handle > the stockcontrol, allocations and assignments of Ipv4 and Ipv6 addresses > for a telecoms company? We use an IP address management tool based on the RIPE Whois server software. One of its main advantages is that is synchronises the assignments with e.g. the official RIPE Whois repository, and sure it can handle your mentioned stock control, allocations and assignments. A presentation I hold at ripe-50 can be found here, however we've added some more functions and IPv6 support in meanwhile: http://www.ripe.net/ripe/meetings/ripe-50/presentations/ripe50-plenary-mon-… An up-to-date introduction will be held at the APRICOT meeting end of February in Bali, I'm sure the slides will be online then as well. If you're interested, I can give you more information off-list. Regards: Tobias - -- Tobias Cremer M.A. IP Admin Engineer Cable & Wireless Telecommunication Services GmbH Landsbergerstr. 155 80687 Muenchen Germany Tel +49 89 926 99 0 -- FAX +49 89 926 99 180 -- COMNET 7 49 9169 www.cw.com/de - -- Every message GnuPG signed -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFvxvThC6y11CNwvcRAnyAAJ91hV74BrSourjf+RsiDrIEZ/VCfgCgj47B ubCoikUsSKWiOqQXCXIsPkY= =WXdl -----END PGP SIGNATURE-----

1 0

RIPE NCC Planned Maintenance, February 2007
by RIPE NCC 29 Jan '07

29 Jan '07

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC will perform planned maintenance work that will affect a number of servers. The maintenance work will take place on: Thursday, 1 February 2007 between 21:00 and 23:00 UTC Wednesday, 7 February 2007 between 21:00 and 23:00 UTC During this maintenance, individual servers may experience short outages. We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to: ops(a)ripe.net

1 0

Deprecation of CRYPT-PW authentication method from the RIPE Database: Start of Phase 2
by Agoston Horvath 10 Jan '07

10 Jan '07

[Apologies for duplicate mails] Dear Colleagues, Phase 2 of the CRYPT-PW deprecation project will start today, Wednesday, 10 January 2007. During this period the following will apply: * Any modification to a maintainer or IRT object that adds a new CRYPT-PW authentication will be rejected * Any modification to a maintainer or IRT object that attempts to replace a CRYPT-PW with another CRYPT-PW will be rejected * Any object creations that include a CRYPT-PW authentication will be rejected * The RIPE Database will add a warning to the acknowledgement message if CRYPT-PW is used during authentication * The RIPE Database will add a warning to the acknowledgement message if a modified maintainer or IRT object still contains existing CRYPT-PW authentication Notification e-mails will be sent today to over 6300 e-mail addresses, concerning a total of 2778 objects with CRYPT-PW authentication only. Another 252 objects have other authentication methods in addition to CRYPT-PW. 20898 maintainers have no CRYPT-PW password at all. If you receive a separate notification e-mail you will have to change your password authentication method to PGP, X.509 or MD5-PW. To change your password authentication method from CRYPT-PW to MD5-PW, use the CGI at: https://www.ripe.net/cgi-bin/crypt2md5.cgi Phase 1 of the project has been successfully completed. One quarter of all objects containing CRYPT-PW authentication have been modified. Over 85% of these changes were made using the crypt2md5.cgi web form. More information about the project is available at: http://www.ripe.net/db/support/security/crypt-pw_deprecation/ *Key dates* Thursday, 30 November 2006: Notification (Phase 1) Wednesday, 10 January 2007: Reject new CRYPT-PW (Phase 2) Wednesday, 21 February 2007: Remove CRYPT-PW from RIPE Database (Phase 3) If you have any questions, contact: ripe-dbm(a)ripe.net. Regards, Agoston Horvath Database Group RIPE NCC

1 0

inetnum object addition - error
by linux baby 09 Jan '07

09 Jan '07

Thanks for your help. Please help me to add the inetnum object. i have created the following RR1-SAMPLE, RR2-SAMPLE - person objects created SAMPLE-MNT - mntner object created I have the inetnum object input file like below --------------- cat /usr/local/src/nic/ipcheck.input inetnum: 10.11.12.0 - 10.11.12.255 netname: NIC-NETWORK descr: THIS IS TESTING RANGE country: IN admin-c: RR1-SAMPLE tech-c: RR2-SAMPLE status: ASSIGNED PA remarks: This network should never be routed outside an enterprise notify: raja(a)nic.in mnt-by: SAMPLE-MNT mnt-lower: SAMPLE-MNT mnt-routes: SAMPLE-MNT password: redhat123 source: SAMPLE changed: raja(a)nic.in 20070109 ------------ i checked the range available by whois -p 43001 -h knagalin.linux2all.net 10.11.12.0 - 10.11.12.255 [Querying knagalin.linux2all.net] [knagalin.linux2all.net] % This is the NIC Whois server. % Note: this output has been filtered. % Information related to '0.0.0.0 - 255.255.255.255' inetnum: 0.0.0.0 + - + 255.255.255.255 netname: + WHOLE-IPV4 + descr: The Whole IPv4 country: NL remarks: Country is really worldwide + admin-c: RDBM-SAMPLE # admin contact tech-c: RDBM-SAMPLE # tech contact status: ALLOCATED PI mnt-by: TEST-DBM-MNT source: SAMPLE # Filtered I try to add in my whois server database [root@knagalin whoisd]# ./bin/dbupdate -c ./conf/rip.config.sample -f /usr/local/src/nic/ipcheck.input SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [inetnum] 10.11.12.0 - 10.11.12.255 ***Info: Syntax check passed inetnum: 10.11.12.0 - 10.11.12.255 netname: NIC-NETWORK descr: THIS IS TESTING RANGE country: IN admin-c: RR1-SAMPLE tech-c: RR2-SAMPLE status: ASSIGNED PA remarks: This network should never be routed outside an enterprise notify: raja(a)nic.in mnt-by: SAMPLE-MNT mnt-lower: SAMPLE-MNT mnt-routes: SAMPLE-MNT source: SAMPLE changed: raja(a)nic.in 20070109 Please tell me where i am making mistake, Please help me to add the inetnum object in my whoisd server database. Waiting for your reply. regards Karthikeyan.N On 1/9/07, RIPE Database Manager <ripe-dbm(a)ripe.net> wrote: > > Dear Karthikeyan.N > > As I pointed out to you yesterday it will be a good idea to read the > > RIPE Database User Manual: Getting Started > http://www.ripe.net/ripe/docs/db-start.html > > This clearly explains how to create objects in the RIPE Database and how > to > query for them. It was written to help new users to get started. > > The answer to your specific problem below is the '# Filtered' comment on > the "source:" line. The update program will not accept updates with > filtered > query output. > > You may also want to check your database naming as you have used nic-hdls > like AA1-TEST with a source of SAMPLE. Maybe these should both be either > TEST or SAMPLE. > > -- > Regards, > Denis Walker > > RIPE Database Administration > > > On Tue, 9 Jan 2007 10:44:19 +0530, Linux Baby wrote: > * hi, > * Can you give me one example for dbupdate command to > * create/delete/update > * objects using commandline/webinterface. > * > * regards > * Karthikeyan.N >

1 0

help sample - dbupdate
by linux baby 09 Jan '07

09 Jan '07

hi, Can you give me one example for dbupdate command to create/delete/update objects using commandline/webinterface. regards Karthikeyan.N

2 1

commandline howto
by linux baby 09 Jan '07

09 Jan '07

Hi, Can you help me howto add the users details in whoisd server either command line or webinterface and query the server. I tried syncupdates but there is no proper doc for the same, Please help me how to add the users details through commandline and howto check the whoisd server for the same. If possible, please help me to configure the syncupdates/webupdates in whoisd server. regards Karthikeyan.N

1 0

update[inetnum] issue
by linux baby 08 Jan '07

08 Jan '07

hi, i am tring to do the addition of inetnum object using 'dbupdate'. input file: [root@knagalin whoisd]# cat /tmp/ipcheck.input inetnum: 10.10.10.0 - 10.10.10.255 netname: IANA-ABLK-RESERVED1 descr: Class A address space for private internets descr: See http://www.ripe.net/db/rfc1918.html for details country: EU # Country is really world wide admin-c: AA1-TEST tech-c: AA2-TEST status: ALLOCATED UNSPECIFIED remarks: This network should never be routed outside an enterprise remarks: See RFC1918 for further information mnt-by: TEST-DBM-MNT mnt-lower: TEST-DBM-MNT mnt-routes: TEST-DBM-MNT source: SAMPLE # Filtered changed: rsm(a)nic.in 20070107 ./bin/dbupdate -c ./conf/rip.config.sample -f /tmp/ipcheck.input ... Create FAILED: [inetnum] 10.0.0.0 - 10.255.255.255 ***Info: Syntax check passed inetnum: 10.0.0.0 - 10.255.255.255 netname: IANA-ABLK-RESERVED1 descr: Class A address space for private internets descr: See http://www.ripe.net/db/rfc1918.html for details country: EU # Country is really world wide admin-c: AA1-TEST tech-c: AA2-TEST status: ALLOCATED UNSPECIFIED remarks: This network should never be routed outside an enterprise remarks: See RFC1918 for further information mnt-by: TEST-DBM-MNT mnt-lower: TEST-DBM-MNT mnt-routes: TEST-DBM-MNT source: SAMPLE # Filtered changed: rsm(a)nic.in 20070107 ***Error: Cannot submit filtered whois output for updates. please help me to add the iprange object in inetnum. Thanks in advance. regards Karthikeyan.N

1 0

ASN32 deployment
by Denis Walker 08 Jan '07

08 Jan '07

[Apologies for duplicate e-mails] Dear colleagues, This morning, between 07:00 and 09:00 (UTC), we deployed new software for the RIPE Database. Three changes were made: 1. The new software allows the creation of 32-bit (4-byte) Autonomous System Numbers (ASNs). There is more information about this in the references at the end of this e-mail. 2. The ORGANISATION object type NON-REGISTRY has been changed to OTHER. The RIPE NCC modified all existing organisation objects which had the old type. There is more information about this at: http://www.ripe.net/ripe/maillists/archives/db-wg/2006/msg00245.html 3. We reversed changes made to the status of ERX objects. While implementing the ASSIGNED ANYCAST status, other changes were made. This prevented more specific assignments from being created within EARLY REGISTRATION ranges. These changes have been rolled back. If you have any questions about any of these changes, send an e-mail to <ripe-dbm(a)ripe.net>. Regards Denis Walker Database Group RIPE NCC -------- References: The new 32-bit ASN format is described in these documents: http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representatio… http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-01.txt Sites using the RIPE Database software will probably have to upgrade their systems. See: http://www.ripe.net/news/asn-db-update.html Our test database (e-mail to <test-dbm(a)ripe.net> or access through webupdates) also now handles the new AS number format.

5 7

NCC#2007010704
by RIPE Database Manager 08 Jan '07

08 Jan '07

Dear Karthikeyan.N Thankyou for your questions regarding the RIPE Database. We will write to you off the working group mailing list and address these issues directly. -- Regards, Denis Walker RIPE Database Administration

1 0

syncupdate login
by osk 03 Jan '07

03 Jan '07

Hi, I am new to this whoisd server, i am doing the whoisd setup for my office, i have done the whoisd server installation, the port is listening. To create and update the information i am triing to use the syncupdates to communicate with database, i am not have the proper doc for syncupdates and webupdates to configure the whoisd setup. Can you help me, how to i configure and use the syncupdates to my whoisd server to update the database regards Karthikeyan.N -- winners don't do different things they do things differently

1 0