- db-wg - mailman.ripe.net

New beta release of the RIPE Database Reimplementation software
by RIPE Database Administration 12 May '00

12 May '00

Dear All, This mail is to notify you of the further progress in the development of the new implementation of the RIPE Database software. The software has a temporary name of RIP, which stands for "Re-Implementation Project". Today, we have made a new prototype of the source code. There have been many changes since the last prototype: most notably, the update functionality has been integrated to the server. You can download this last prototype at the following URL: ftp://ftp.ripe.net/ripe/dbase/reimp/RIP-0.3.0beta2.tar.gz You can also test the functionality of this prototype of the RIP whois server in 2 ways: - By querying the host reimp.ripe.net at port 43; you will find there a Near-Real-Time Mirror in RPSL format of the live RIPE Database. - By using the RIP Test Database. You can send test updates to this database at the address <auto-rip(a)ripe.net>, and you can query this database at reimp.ripe.net port 4343. Please note the following things when sending updates to the RIP Test DB: - you will get very simple acknowledgements; - mntner, as-block and aut-num objects cannot be created yet; - no notifications are being sent to the "notify" addresses. We would be very pleased if you could test the new implementation in both ways, and let us know your opinions. Please let us also know of any bugs you can find. Please send your comments to the <db-beta(a)ripe.net> mailing list. To subscribe to this list, send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. This is a moderated mailing list so some delays in subscription are possible. If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Marek Bukowy ____________________________ RIPE Database Administration.

1 0

Top 100 Maintainers List 20000509
by RIPE Database Administration 09 May '00

09 May '00

1 0

Top 100 Maintainers List 20000425
by RIPE Database Administration 25 Apr '00

25 Apr '00

1 0

RE: DB consistancy checking tools
by Matthew Robinson 18 Apr '00

18 Apr '00

Firstly my sincere apologies for not sorting something out earlier. I've spent most of my time either building networks or looking after my son Lewis, born 26/03/2000 (two weeks late), weighing 5450g or 12lbs 4oz (I like to over engineer)! The hospital didn't include any instructions and despite several detailed searches I have been unable to locate either a RIPE document or RFC detailed care of a newborn baby! Are people still interested in the idea of a users forum as described below and should we try to have a BoF in Budapest or do we still need more of an list based discussion? -----Original Message----- From: Wilfried Woeber, UniVie/ACOnet [mailto:woeber@cc.univie.ac.at] Sent: 20 January 2000 14:55 To: matthew(a)planet.net.uk Cc: lir-wg(a)ripe.net; db-wg(a)ripe.net; woeber(a)cc.univie.ac.at Subject: RE: DB consistancy checking tools Matthew, I think this is an interesting proposal: >I have been wondering recently whether a separate group should be set up for >the sole purpose of creating tools/advise/methods/hints 'n' tips for LIR's >to keep on top of their entries and make management easier. A sort of RIPE >users working group not concerned with designing objects for the database >but how to put existing objects in it, remove them, manage them, etc. > >My 2c > >Matthew To start things moving, could you come up with a coarse draft of ideas and short-term goals to take up? On the more formal side, one of the possible solutions to accomodate that activity might be to create a TaskForce to work on well-defined items during RIPE35 (do you intend to particpate?). This TF might be supported by both LIR and DB, or sponsored by whichever group is seen to be appropriate...

1 0

Top 100 Maintainers List 20000412
by RIPE Database Administration 12 Apr '00

12 Apr '00

1 0

no answer from the RIPE NCC mail-distribution-robot...
by Bornhorst, Ludger 06 Apr '00

06 Apr '00

Hello All, since Tuesday, 04.04.2000 I sent three mails to the RIPE NCC hostmaster account 1. Mail for Ticket NCC#2000012331 2. Mail for Ticket NCC#2000036750 3. Mail for a new address request (no Ticketno yet) and nothing happened. Normally I get a response from the RIPE NCC mail-distribution-robot within minutes, or at least hours. Now it is Thursday and the Mails haven't bounced, so I think they must have been received by someone. Maybe there is a failure at the RIPE NCC mail-distribution-robot...? Am I alone with this, or did anyone have the same experience? kind regards +-----------------------------------------------------------------------+ | Ludger Bornhorst Ludger.Bornhorst(a)telekom.de | | Deutsche Telekom AG | | Network Information Center tel +49 441 234 4581 | | Oldenburg, Germany fax +49 441 234 4589 | +-----------------------------------------------------------------------+

2 1

Re: no answer from the RIPE NCC mail-distribution-robot...
by henning.brauer＠bsmail.de 06 Apr '00

06 Apr '00

Hi all, having the same probs. Normally I had answers within minutes, now it's days. There are some hard performance problems at Ripe as far as i were informed what makes our business no easier... Greetings from Germnay Henning Brauer ------------------------------------------------------------ BS Web Services part of Mediadeck Rödingsmarkt 14 20459 Hamburg Germany Fon (040) 37 503 57-0 Fax (040) 37 503 57-5 www.bsws.de info(a)bsmail.de "Bornhorst, Ludger" <Ludger.Bornhorst@t To: db-wg(a)ripe.net elekom.de> cc: "'ripe-dbm(a)ripe.net'" <ripe-dbm(a)ripe.net> Sent by: Subject: no answer from the RIPE NCC mail-distribution-robot... owner-db-wg(a)ripe.ne t 06.04.00 08:56 Hello All, since Tuesday, 04.04.2000 I sent three mails to the RIPE NCC hostmaster account 1. Mail for Ticket NCC#2000012331 2. Mail for Ticket NCC#2000036750 3. Mail for a new address request (no Ticketno yet) and nothing happened. Normally I get a response from the RIPE NCC mail-distribution-robot within minutes, or at least hours. Now it is Thursday and the Mails haven't bounced, so I think they must have been received by someone. Maybe there is a failure at the RIPE NCC mail-distribution-robot...? Am I alone with this, or did anyone have the same experience? kind regards +-----------------------------------------------------------------------+ | Ludger Bornhorst Ludger.Bornhorst(a)telekom.de | | Deutsche Telekom AG | | Network Information Center tel +49 441 234 4581 | | Oldenburg, Germany fax +49 441 234 4589 | +-----------------------------------------------------------------------+

1 0

RIPE Database main server up and running again
by RIPE Database Administration 28 Mar '00

28 Mar '00

Dear All, Thank you for your patience. The RIPE Database main server is now up and running again. The queue of updates is being processed, but please take into account that it will take several hours to clear the queue. Technical details: The failure of one of the memory modules of the server caused a parity error, thus forcing the kernel to panic. The memory module had to be replaced and tested. We are very sorry for the inconvenience caused. If you have any questions or comments, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration.

1 0

Whois service running on a backup server
by RIPE Database Administration 28 Mar '00

28 Mar '00

Dear Colleagues, Unfortunately this morning the main RIPE Whois server experienced a hardware crash. We switched the service to a backup server; thus you may find that the response time for whois queries is longer than usual. The updates are currently not being processed, but they are queued; they will be processed as soon as the main server is up and running again. There is no need to resend your updates. We are currently working to repair the hardware damage on the main server, and we hope to return to the normal situation as soon as possible. Please accept our apologies for this inconvenience. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration. P.S.: Apologies if you receive this mail more than once.

1 0

New DB release 2.3.1
by RIPE Database Administration 21 Mar '00

21 Mar '00

Dear colleagues, We have made available the new release of RIPE Perl database software at our fto site. You can find it at ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.3.2.tar.gz Please find attached notes of the new release. Please note that CLIENTADDRESS type of referral can be used in our production server readily. Best regards, RIPE NCC DB Group ----------------- RELEASE NOTES for RIPE Database 2.3.2 This is mainly a bugfix release, without major new features added. There are also a few maintenance and performance-related changes, and an important security fix. SUPPORTED SYSTEMS This release has been tested with perl 5.00502 on BSDI3.1 and perl 5.00404 on Solaris 2.6 systems. Please let us know if you have problems running it on other systems. NEW FEATURES - New type of referral: CLIENTADDRESS o A fourth kind of referral is defined, CLIENTADDRESS (The other three were RIPE, INTERNIC and SIMPLE). o The IP address of the client is sent to the referred whois server, if the referral type is CLIENTADDRESS. o The IP address is sent using the -V flag. The version and the IP address will be separated by a comma (eg, -Vripe2.3.1,193.140.45.45). o No other flag will be forwarded to the referred whois server. o When the server gets such a request, it checks the IP number of the server which does the referral against a list of authorized whois servers. If it is not in the list, it will be rejected. The list is named AUTHORIZEDFORREFERRAL in the configuration. o Then, the IP address of the client is extracted from the -V flag string and it will be regarded as if it is the IP address of a directly querying whois client (ie, it is checked against the list of DENYWHOISACCESS list). MAINTENANCE RELATED CHANGES - Introduced some debugging functionality: WHOISDSTAT - creation of files describing the activity of whoisd query processes. Those are normally deleted if the whoisd exits the normal way. WHOISDSTAT is a base filename for those files. - Introduced some limitation on bad clients: QUERYLOOPLIMIT defines a limit for '-k' connections. If more than so many queries for the same search term are detected, QUERYLOOPTXT is printed and the connection is closed. Mainly meant to protect against ptraceroute parsing broken as-macros. SECURITY FIXES - On February 2, 2000, we got a report for a possible buffer overflow in whoisd. An extremely long and specific query, such as the following: % whois `perl -e '{print "0." x 20000}'`(a)joshua.ripe.net (query example from a Linux host; it does not work, of course, if the client has built-in query size limits) caused the forked server process to crash with a segmentation fault. We immediately introduced a patch on whoisd.pl, truncating the queries to 255 characters immediately after they were being read. BUG FIXES - cross-misc: now the sender of cross-notifications is set to HUMAILBOX. - whoisd.pl: o the text for DENIED connection was mistakenly printed on STDOUT. o The timeout handler would wait infinitely to print a msg about closing the connection. Now an alarm has been set up to stop it, the message can be printed to WHOISDSTAT file if active. PERFORMANCE FIXES - addkey: The overflow file handling has been modified, so that it would use a smaller amount of memory.

1 1