- db-help - mailman.ripe.net

Inserting objects in the ripe test
by Ishwinder Singh 06 Apr '12

06 Apr '12

Hi All, I am trying to create an inetnum type of object in the ripe test database but i am unable to get past the eternal authorization error. The Maintainer in the test db that i am using is IS-MNT and i am requesting the ip range 193.0.0.0 - 193.0.0.255 (I am not sure if this should be a valid range for test db purposes but i assume that i should be able to get an inetnum in test db at any range). I have tried with maintainer IS11260-MNT(organization's maintainer) as well to no relief. I am sure that i have entered the correct session password on the passwords list. After doing all this i keep getting the following error: rom-Host: 124.253.3.194 - Date/Time: Fri Apr 6 09:43:11 2012 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] 193.0.0.0 - 193.0.0.255 ***Error: Authorisation failed ***Info: Syntax check passed inetnum: 193.0.0.0 - 193.0.0.255 netname: Test-Network descr: Testing for IS country: NL admin-c: IS1-TEST tech-c: IS1-TEST status: ASSIGNED PA mnt-by: IS-MNT mnt-by: IS11260-MNT changed: ishwinder(a)enbake.com source: TEST ***Warning: Date '20120406' added to changed: attribute 'ishwinder(a)enbake.com' ***Info: Authorisation for parent [inetnum] 0.0.0.0 - 255.255.255.255 using mnt-lower: not authenticated by: TEST-DBM-MNT ***Info: Authorisation for [inetnum] 193.0.0.0 - 193.0.0.255 using mnt-by: authenticated by: IS-MNT, IS11260-MNT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions:http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Can someone guide on what i am doing wrong here and how i can create a inetnum object? Thanks in advance -- Thanks & Regards,

1 0

whois.ripe.net seems dead over v6, working over v4.
by Andy Davidson 05 Apr '12

05 Apr '12

Dear colleagues, I am having timeout problems reaching whois.ripe.net over v6 this morning. In other words, it seems dead over v6. andy@chilli:~$ whois -h 193.0.6.135 ajbd-ripe % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to 'AJBD-RIPE' person: Andy Davidson address: Sheffield phone: +44-1143190605 nic-hdl: AJBD-RIPE remarks: Up the Mariners! mnt-by: MNT-AJBD source: RIPE # Filtered % This query was served by the RIPE Database Query Service (proxy) version 1.4.6 (WHOIS3) andy@chilli:~$ whois -h 2001:67c:2e8:22::c100:687 !$ whois -h 2001:67c:2e8:22::c100:687 ajbd-ripe Timeout. andy@chilli:~$ traceroute6 2001:67c:2e8:22::c100:687 traceroute to 2001:67c:2e8:22::c100:687 (2001:67c:2e8:22::c100:687) from 2001:67c:188:2::10, 30 hops max, 16 byte packets 1 2001:67c:188:2::1 (2001:67c:188:2::1) 1.613 ms 1.728 ms 2.18 ms 2 ge-1-0-8-314.rt0.the.uk.goscomb.net (2a01:348:0:4:0:24:0:1) 0.226 ms 0.197 ms 0.186 ms 3 ae0-700.rt0.sov.uk.goscomb.net (2a01:348::32:0:1) 0.382 ms 0.359 ms 0.336 ms 4 2a01:348::51:0:1 (2a01:348::51:0:1) 0.38 ms 0.386 ms 0.329 ms 5 linx-2601.ge-0-1-0.jun1.thn.network.bit.nl (2001:7f8:4::323b:1) 0.729 ms 0.611 ms 0.586 ms 6 806.xe-0-0-0.jun1.bit-2a.network.bit.nl (2001:7b8:0:326::1) 15.06 ms 14.884 ms 15.058 ms 7 gw.ipv6.amsix.telrtr.ripe.net (2001:7f8:1::a500:3333:2) 18.948 ms 18.986 ms 18.904 ms 8 * * * ^C

2 2

AS16022 - Edit (aut-num) object due to new BGP Upstream
by Yiannis Psaropoulos 30 Jan '12

30 Jan '12

Hi all, We have added a new BGP Upstream (AS174) which we want to be more preferable both inbound and outbound. Below is aut-num object definition. aut-num: AS16022 as-name: COSMOLINE descr: COSMOLINE TELECOMMUNICATION SERVICES S.A. remarks: Athens, GR import: from AS12653 action pref=20; accept ANY export: to AS12653 action aspath.prepend (AS16022, AS16022, AS16022, AS16022); announce AS16022 import: from AS174 action pref=10; accept ANY export: to AS174 announce AS16022 org: ORG-CS6-RIPE admin-c: CDD76-RIPE tech-c: CDD76-RIPE mnt-by: COSMOLINE-MNT mnt-by: RIPE-NCC-END-MNT changed: <mailto:hostmaster@ripe.net> hostmaster(a)ripe.net 20100316 changed: <mailto:i.psaropoulos@cosmoline.com> i.psaropoulos(a)cosmoline.com 20120130 source: RIPE However we still see a large percentage of total inbound traffic coming in from AS12653. Do you think that the aut-num definition update (above) will influence that behavior? Is the aut-num definition truly mapping our routing policy? Given that we updated the aut-num object today, when the changes are expected to have an effect on ISP routers that are using RIPE DB for routing decisions (rpsl) ? Kindest regards, <http://www.cosmoline.com/> cid:image002.gif@01CC2071.DD8F4890 Yiannis Psaropoulos Data Network Engineer, MBA Cosmoline 40th km Attiki Odos Rest Area Mesogeia 190 02 Peania, Greece my: phone +30 212 212 2212 my: mobile +30 6932 311 121 jn_certified_specialist_rgb.gifccna_med.gif ΕΙΔΟΠΟΙΗΣΗ ΑΠΟΡΡΗΤΟΥ: Οι πληροφορίες που περιλαμβάνονται στο παρόν είναι εμπιστευτικές και απευθύνονται αποκλειστικά προς τον παραλήπτη που αναφέρεται παραπάνω. Εάν το μήνυμα που ακολουθεί δεν προορίζεται για σας, σας γνωρίζουμε ότι δεν δικαιούσθε και είναι παράνομο να το αναγνώσετε, αντιγράψετε, διανείμετε ή χρησιμοποιήσετε με οποιοδήποτε τρόπο. Σας παρακαλούμε ακόμη να ειδοποιήσετε αμέσως τον αποστολέα στην τηλεφωνική σύνδεση που αναφέρεται ή με απαντητικό e-mail και να καταστρέψετε το πρωτότυπο. IMPORTANT NOTICE: This email and any of its attachments are intended only for the recipient(s) named above and are confidential and/or contain trade secrets. Any unauthorized use, e.g. review, printing, copying or distribution by other persons, is prohibited and may constitute a criminal offence. If you have received this email in error, please notify the sender immediately and delete the original message.

2 3

RIPE Object Update
by Michelle Pooley 11 Jan '12

11 Jan '12

Hi, We need to add a new mnt-by to our AS15510 object in the RIPE DB, however the mntner currently protecting it is AS1849 and we don't have the authorisation. This is a legacy issue as this building used to be owned by PIPEX. I have tried to get in touch with the contacts listed for AS1849 but received no response. Does anyone have a suggestion on how I can get this sorted? aut-num: AS15510 as-name: UNSPECIFIED descr: Compuweb Communication Services Ltd import: from AS1849 action pref=100; accept ANY export: to AS1849 announce {194.216.112.0/23} export: to AS1849 announce {194.116.174.0/23} export: to AS1849 announce {195.8.126.0/24} default: to AS1849 action pref=100; networks ANY admin-c: KM2537-RIPE <http://apps.db.ripe.net/whois/lookup/ripe/person-role/KM2537-RIPE.html> tech-c: KM2537-RIPE <http://apps.db.ripe.net/whois/lookup/ripe/person-role/KM2537-RIPE.html> mnt-by: RIPE-NCC-END-MNT <http://apps.db.ripe.net/whois/lookup/ripe/mntner/RIPE-NCC-END-MNT.html> notify: support(a)uk.uu.net mnt-by: AS1849-MNT <http://apps.db.ripe.net/whois/lookup/ripe/mntner/AS1849-MNT.html> changed: hostmaster(a)ripe.net 20000721 source: RIPE changed: daniel.hehir(a)uk.mci.com 20040514 changed: andrea.agering(a)se.mci.com 20050902 Best Wishes Michelle Pooley Technical Support Manager Description: new-logo2.gif Tel: 0845 203 1000 mpooley(a)cwcs.co.uk http://www.cwcs.co.uk <http://www.cwcs.co.uk/> Description: Do you need to print this email? ----------------------------- This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. CompuWeb Communications Services Limited (Registered in England No. 3798604) T/AS CWCS Managed Hosting, its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt.

2 1

Digest intervals
by Thor Kottelin 30 Dec '11

30 Dec '11

Due to low traffic, db-help digests are being sent very infrequently. As an example, the one I received today contained messages posted on 6, 8 and 15 December. This problem can be fixed by setting the mailing list software to send digests at least once a day whenever there are messages. Would you like the RIPE NCC to make such a change? -- Thor Kottelin http://www.anta.net/

1 0

creating inet6num objects in RIPE database for customer IPv6 networks
by Martin T 15 Dec '11

15 Dec '11

I work in a company where we have been very strict with documenting and creating inetnum objects in RIPE database for IPv4 addresses, which we have allocated to our customers(from /31 networks to /24). However, for IPv6 we have only created inet6num object to our huge /32 IPv6 network, but none of the customer allocations(usually /48) are documented in RIPE database. Should one do this? Is this mandatory? In addition, as I have understood, one might get into trouble if he doesn't document it's IPv4 addresses in RIPE(lose it's allocation)- does the same apply to IPv6 addresses as well? I mean might we lose our /32 IPv6 network if we proceed with current practise and not register customer IPv6 allocations in RIPE database? regards, martin

1 0

RIPE and DNS delegations for provider independent addresses
by Martin T 08 Dec '11

08 Dec '11

In case "companyA" has /24 provider independent network allocated by RIPE, which has RIPE NCC as a first maintainer and "companyA" maintainer object as a second maintainer, then is "companyA" able to delegate reverse DNS queries to the DNS server it prefers? Or should "companyA" contact RIPE NCC in order to get reverse delegation(http://www.ripe.net/data-tools/dns/reverse-dns) done? In addition, if I know the provider independent IP address, then is it possible to view the delegated DNS server using the whois.ripe.net database? So far I have used "dig +trace -x I.I.P.P" and followed the chain of delegations. regards, martin

1 0

"org:" field in person object
by Martin T 06 Dec '11

06 Dec '11

In person object template, there is an "org:" field: martint@T60:~> whois --version Version 4.7.5. Report bugs to <md+whois(a)linux.it>. martint@T60:~> whois -h whois.ripe.net -t person | grep org org: [optional] [multiple] [inverse key] martint@T60:~> As I understand, this is for organization object(?). In which case this is needed? So far I have never seen a person object with "org:" specified.. regards, martin

2 1

which attributes support inverse search?
by Martin T 06 Dec '11

06 Dec '11

Hi, which attributes inRIPE database are inverse searchable? I know one can use "origin"(for example "whois -Brh whois.ripe.net -i origin AS3249") and "person", but are there other practically usable attributes, which support inverse search? regards, martin

2 1

best practice for "changed:" field
by Martin T 05 Dec '11

05 Dec '11

As I understand, in RIPE database every object has a mandatory "changed" field. There can be multiple "changed" fields. Is it a good practice to keep all the changes made to the object? What are the advantages and disadvantages? regards, martin

2 1