- db-wg - mailman.ripe.net

Re: [db-wg] 3.2.0 make_db getvar cores
by Randy Bush 19 Dec '03

19 Dec '03

> Everything seems OK in your config files you've sent. I could not > replicate your problem. My best bet is that, in rip.config > SOURCEFILE /usr/home/whois/conf/sources.config > points to a file which is _not_ the one you've sent. sigh. with that gdb output? puhleeze! (gdb) back #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 #1 0x8050147 in ca_readSources ( sourcesDefFile=0x80c2840 "/usr/home/whois/conf/sources.config", confVars=0x80b1840) at ca_sourceLoader.c:464 #2 0x804faa2 in ca_init (configFile=0xbfbff9b1 "../conf/rip.config") at ca_initFn.c:87 #3 0x804bc2f in main (argc=7, argv=0xbfbff858) at getvar.c:84 let me try to debug by turning on debugging in ca_sourceLoader.c # /usr/home/whois/utils/getvar -s SAMPLE -c /usr/home/whois/conf/rip.config -p dbhost Inside ca_readSources() function. Sources file is: /usr/home/whois/conf/sources.config We are reading a comment or an empty line ..... line:DATABASE SAMPLEDB:End of line Length of line: 17 LINE >>>DATABASE SAMPLEDBEND_OF_LINE Beginning of a database defintion ..... Database name is: SAMPLEDB line:host: localhost:End of line Length of line: 16 LINE >>>host: localhostEND_OF_LINE tokens[0] = host tokens[1] = localhost VarName: host; dbComp: localhost line:port: 3306:End of line Length of line: 11 LINE >>>port: 3306END_OF_LINE tokens[0] = port tokens[1] = 3306 VarName: port; dbComp: 3306 line:trx_support: n:End of line Length of line: 14 LINE >>>trx_support: nEND_OF_LINE tokens[0] = trx_support tokens[1] = n VarName: trx_support; dbComp: n line:user: rip:End of line Length of line: 10 LINE >>>user: ripEND_OF_LINE tokens[0] = user tokens[1] = rip VarName: user; dbComp: rip line:password: secret:End of line Length of line: 19 LINE >>>password: secretEND_OF_LINE tokens[0] = password tokens[1] = secret VarName: password; dbComp: secret line:/DATABASE:End of line Length of line: 9 LINE >>>/DATABASEEND_OF_LINE We have reached the end of a DATABASE definition Testing the population of the db structure: localhost::3306::n::rip::secret:: ^ wowie zowie! no database name ^ the very problem we sought guess what happens when the password is nine characters! .../ripe-dbase-3.2.0# grep -c strcpy ./modules/ca/ca_sourceLoader.c 16 oh wonderful and thanks a million for the debugging help randy

1 0

3.2.0 make_db getvar cores
by Randy Bush 17 Dec '03

17 Dec '03

o freebsd 4.9-stable, quite recent o all ports just rebuilt o wanted to do a clean fresh install of whois 3.2.0, as i could not successfully convert o successful build o successful install conf/rip.config same as used for 3.1.1 excpt did emacs diff merge to get the syntax changes conf/sources.rip same as used for 3.1.1 except added trx_support: n in mysql, i deleted both databases, RIPADMIN and dbrgnet /scripts# ./make_db -c ../conf/rip.config -s RGNET -0 Error: Non-existent database "dbrgnet" referenced !!! died: +792 ca_sourceLoader.c Segmentation fault (core dumped) ************** ERROR *************** *** 05:19:01 unknown source RGNET ************************************ # gdb /usr/local/src/net/ripe-dbase-3.2.0/utils/getvar/getvar getvar.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf Core was generated by `getvar'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libgthread12.so.3...done. Reading symbols from /usr/local/lib/libglib12.so.3...done. Reading symbols from /usr/local/lib/mysql/libmysqlclient_r.so.10...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libcrypt.so.2...done. Reading symbols from /usr/lib/libpam.so.1...done. Reading symbols from /usr/lib/libcipher.so.2...done. Reading symbols from /usr/local/lib/libxml2.so.5...done. Reading symbols from /usr/local/lib/libiconv.so.3...done. Reading symbols from /usr/local/lib/libxslt.so.2...done. Reading symbols from /usr/lib/libc_r.so.4...done. Reading symbols from /usr/lib/libz.so.2...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 792 die; (gdb) back #0 0x805087d in ca_parseSrcLine (lineStr=0xbfbff74c "database:\tdbrgnet", srcStructPtr=0x80c8400) at ca_sourceLoader.c:792 #1 0x8050147 in ca_readSources ( sourcesDefFile=0x80c2840 "/usr/home/whois/conf/sources.config", confVars=0x80b1840) at ca_sourceLoader.c:464 #2 0x804faa2 in ca_init (configFile=0xbfbff9b1 "../conf/rip.config") at ca_initFn.c:87 #3 0x804bc2f in main (argc=7, argv=0xbfbff858) at getvar.c:84 randy

2 2

Re: [sed] problem updating database to 3.2.0
by Randy Bush 17 Dec '03

17 Dec '03

engin pointed out my stupid, using the admin db as opposed to the whois db. but now i fail on the last set # mysql -ufoo -pbar -Ddbrgnet -e'ALTER TABLE acl ADD COLUMN threshold tinyint(3) unsigned Default '4' NOT NULL after trustpass' $SOURCE ERROR 1146 at line 1: Table 'dbrgnet.acl' doesn't exist # mysql -ufoo -pbar -Ddbrgnet -e'ALTER TABLE acl ADD COLUMN maxconn tinyint(3) unsigned Default '6' NOT NULL after threshold' $SOURCE ERROR 1146 at line 1: Table 'dbrgnet.acl' doesn't exist another clue by four please randy

2 1

problem updating database to 3.2.0
by Randy Bush 16 Dec '03

16 Dec '03

running 3.1.1 and trying to get to 3.2.0 first line of UPDATING fails # mysql -ufoo -pbar -DRIPADMIN -e'ALTER TABLE names DROP PRIMARY KEY' ERROR 1146 at line 1: Table 'RIPADMIN.names' doesn't exist clue-by-four please randy

1 0

Announcement Routing Registry Training Courses
by RIPE NCC Training 16 Dec '03

16 Dec '03

------- Dear Colleagues, [apologies for duplicate postings] As a service to its members the RIPE NCC offers the "Routing Registry Training Course". The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using (RPSL) Routing Policy Specification Language and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course. It will: - NOT teach the basics of routing - NOT teach the basics of RIPE Database operations, - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. Hostmasters) . It is assumed that all attendees will be familiar with Border Gateway Protocol routing and with the RIPE Database (i.e. creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with the following: - A working Ethernet card, - Three meters of Ethernet cable, - A secure connection client, - A web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership fee. More information about the Routing Registry Training Course can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a Routing Registry Training Course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this e-mail and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either: - be an LIR contact - be confirmed by an LIR contact LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the Routing Registry Training Course will not be an authoritative contact person for their LIR, and therefore will be, refused by the course registration "robot". In order to be admitted to the course, a confirmation e-mail must be sent to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, Training Team RIPE NCC ************************************************************************* COURSE DATES AND VENUES ======================== Date: Friday 6 February 2004 Time: 0900 - 1700 Location: Amsterdam, The Netherlands AND: Date: Tuesday 17 February 2004 Time: 0900 - 1700 Location: Tehran, Iran AND: Date: Friday 5 March 2004 Time: 0900 - 1700 Location: Rome, Italy AND: Date: Friday 23 April 2004 Time: 0900 - 1700 Location: Istanbul, Turkey AND: Date: Friday 14 May 2004 Time: 0900 - 1700 Location: Bratislava, Slovakia AND: Date: Thursday 24 June 2004 Time: 0900 - 1700 Location: Stockholm, Sweden ************************************************************************* REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The course you plan to attend (date and location) # COURSE [ ] %END

1 0

RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
by Daniel Roesen 10 Dec '03

10 Dec '03

Hi, $ whois -h whois.ripe.net 204.152.184.85 [...] inetnum: 0.0.0.0 - 255.255.255.255 netname: IANA-BLK descr: The whole IPv4 address space [...] and nothing else. The referral to ARIN for 204/8 is missing. I've checked a couple of other RIRs /8s which all had the same problem. Was there a deliberate change that I missed? Best regards, Daniel

2 5

Deprecation of "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database
by Katie Petrusha 05 Dec '03

05 Dec '03

[ Apologies for duplicate messages ] Dear colleagues, "cross-nfy:" and "cross-mnt:" attributes will be deprecated in the RIPE Whois Database by 1 February 2004. The RIPE Whois Database previously had a cross notification mechanism. This mechanism used "cross-nfy:" and "cross-mnt:" attributes of route and aut-num objects to notify particular maintainers and contacts when an overlapping route object had been added or removed. In May 2003, this mechanism was deprecated, as it is already covered by Routing Policy System Security functionality. In March 2003, the proposal was circulated to deprecate "cross-nfy:" and "cross-mnt:" attributes in the RIPE Whois Database as they are no longer needed: http://www.ripe.net/ripe/mail-archives/db-wg/2003/msg00035.html Approximately 180 aut-num and 620 route objects will be affected by this change. These objects should be modified before 1 February 2003 and the "cross-nfy:" and/or "cross-mnt:" attributes should be removed from them. As soon as these attributes have been deprecated, they will not be accepted in the RIPE Whois Database. Therefore, we encourage everyone to make the necessary modifications in advance. The RIPE Database Administration will update the objects still requiring modifications to change deprecated attributes into "remarks:" attributes. No individual notifications will be sent. Relevant maintainers will be notified via the usual RIPE Whois Database notification mechanism. This information can be found at: http://www.ripe.net/db/cross_nfy_mnt_deprecation.html -- Katie Petrusha Software Engineering Department RIPE NCC

1 0

Announcement: Redirecting reverse DNS updates
by RIPE Database Manager 05 Dec '03

05 Dec '03

Dear Colleagues, From 8 December 2003, as part of the effort to streamline reverse DNS operations, domain updates that contain in-addr.arpa or ip6.arpa type entries sent to <auto-dbm(a)ripe.net> will automatically be forwarded to <auto-inaddr(a)ripe.net> for processing. This will continue until the two processes are combined into one. Such updates will be processed as follows: - If the update contains only domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa' , it will be redirected to: <auto-inaddr(a)ripe.net> - If the update contains a mixture of domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa', as well as other types of database objects, the message will be rejected. The user will receive an e-mail requesting that the objects be separated and re-submitted. - All other e-mails will be processed as normal. - It will not be possible to update these domain objects using syncupdates. Please don't hesitate to contact <ripe-dbm(a)ripe.net> for questions, comments or suggestions. Regards, -- Can Bican Software Engineering Department RIPE NCC

1 1

Domain Cleanup Proposal
by RIPE Database Manager 03 Dec '03

03 Dec '03

Dear Colleagues, A. Introduction This proposal is part of the effort to streamline reverse DNS operations [1] and make it easier for network range users to manipulate related domain objects. Local Internet Registries (LIRs) maintain their reverse delegations at the RIPE NCC through the use of domain objects. For several historical reasons there are a number of inconsistencies between the domain objects and the reverse delegation information in the DNS. Since we want to move to a system in which the Whois Database is the authoritative source for data that is published in the DNS (see [1]), there is a need to remove these inconsistencies. In this proposal, we will address the inconsistencies between data represented through the domain objects in the Whois Database and the reverse delegation data in our zone-files. We will also propose solutions to fix these inconsistencies. Note, this proposal is only relevant for domain objects that the RIPE NCC provides reverse delegation services for i.e. networks delegated to it by the Internet Address and Numbering Association (IANA) and networks transferred to the RIPE Database via the Early Registration Transfer (ERX) Project [2]. This proposal is NOT relevant to domains in the e164.arpa space. B. Type of Inconsistencies - Domain objects that have no delegation in the zone configurations: Reverse DNS-related updates to the RIPE database must be sent to <auto-inaddr(a)ripe.net>, otherwise zone configurations can not be updated. There are objects in the RIPE Database created via methods other than by sending an e-mail to <auto-inaddr(a)ripe.net>, causing this type of inconsistency. - Zone configuration entries that do not exist as domain objects in the RIPE Database: When zone files are updated manually, and not by sending an e-mail to <auto-inaddr(a)ripe.net>, this type of inconsistency occurs. - Conflicting entries in the RIPE Database and zone files: A mismatch between the "nserver:" attributes and the NS Resource Records (RRs) in our zone files occurs as a mixture of the first two inconsistencies. The domain object has been added or modified at one point via <auto-inaddr(a)ripe.net>, but then either updated manually or by <auto-dbm(a)ripe.net>. - Invalid domain objects in the RIPE Database: This type of inconsistency occurs in domain objects that can not map to a valid DNS entry. As an example, 8080.80.in-addr.arpa is an invalid entry. Only reverse address space mapping is taken into account. - Invalid "nserver:" attributes in the RIPE Database: "nserver:" attributes must contain hostnames rather than IP entries. This type of inconsistency occurs when one of the "nserver:" attributes does not contain a host name. C. Preventive remedies - Enforcing domain updates to <auto-inaddr(a)ripe.net> We are in the process of integrating <auto-inaddr(a)ripe.net> and <auto-dbm(a)ripe.net>, so that domain updates and other types of updates can be performed from the same source. Until then, in order to prevent further inconsistencies, updates sent to <auto-dbm(a)ripe.net> containing only reverse domain objects will automatically be forwarded to <auto-inaddr(a)ripe.net>. Updates that contain a mixture of domain and other types of objects will be returned to the user unprocessed, warning him/her to split the objects and resend. A separate announcement has already been sent to related mailing lists about this change. D. Clean-up of Inconsistencies The goal of the clean-up is to streamline the contents of domain objects and zone configuration files so that we can create zone files from the Whois Database. If choices have to be made about which data is more accurate , the data in the DNS has prevalence over the data in the Whois Database. The approach followed in the clean-up is to identify inconsistencies, notify the contact persons for the domain objects, provide them with a suggested fix and allow maintainers to fix their objects (details below). After about six weeks the RIPE NCC will send messages about inconsistencies still present in the system. Two weeks after this message has been sent, the RIPE NCC will apply the suggested fix to the domain objects automatically. - Domain objects that do not exist in zone configurations: Contact persons(*) in the domain object will be notified that the object will be deleted by the given deadline unless it is updated. This procedure will be followed even if the domain object contains valid delegation information. Resubmitting the object will ensure that a valid delegation is created in the DNS. - Zone configuration entries that do not exist as domain objects in the RIPE Database: The contact persons(*) in the less specific inetnum object will be notified that, at a given deadline, place holder records in the RIPE Database will be created for these objects. These can be overridden by the maintainer of the inetnum object. The notification contains a suggested domain object that can be modified and submitted before the deadline if the LIR does not want to have a domain object created automatically. - Conflicting entries in the RIPE Database and zone files: Contact persons(*) in the domain object will be notified that the object will be updated to reflect the contents of the delegation NS RR in the reverse zone files by the given deadline. They will be notified that they can fix these entries by updating them. The notification contains a suggested domain object that can be modified and submitted before the deadline if the LIR does not want to have a domain object modified automatically. The clean-up is not meant to solve lame delegation data (e.g. when the NS RRs at the parent side are different from NS RRs at the child side of a zone). Therefore the suggested domain object might not represent the actual set of authoritative nameservers and fail during submission by the maintainer. - Invalid domain objects in the RIPE Database: Contact persons(*) in the domain object will be notified that the object will be deleted by the given deadline. - Invalid "nserver:" attributes in the RIPE Database: Contact persons(*) in the domain object will be notified that the contents of the "nserver:" attributes will be replaced by the entries in zone files if there are any, otherwise the object will be deleted. One IP address may refer to many hostnames, therefore automatically replacing it with its host entry may be erroneous. *: Contact persons are defined by the NIC handles listed in the "admin-c:", "tech-c:", "zone-c:" and the "mnt-by:" attributes of the domain object. E. Timeline - 7/12/2003: Filtering domain updates to <auto-dbm(a)ripe.net>. Domain objects submitted to <auto-dbm(a)ripe.net> are redirected to the <auto-inaddr(a)ripe.net> interface. - 3/12/2003: An announcement will be sent to the Database WG and DNS WG mailing lists - January 2004:Listing inconsistencies and sending notifications to contact persons. - End of February 2004 (announced approximately two weeks before): Cleanup (creation of place holder records and synchronising conflicting entries) This timeline allows for a two month period in which customers are informed and have the opportunity to fix inconsistencies. The end of February milestone is tentative and may extended during the cleanup if unexpected problems are encountered. E. References [1]: Original proposal http://www.ripe.net/reverse/proposal.html. Discussion on this proposal has taken place on the RIPE NCC Services WG mailing list and was summarised in: http://www.ripe.net/ripe/mail-archives/ncc-services-wg/2003/msg00361.html [2]: Early Registration Transfer [ERX] Project http://www.ripe.net/db/erx/erx-ip/ Regards, -- Can Bican Software Engineering Department Olaf Kolkman New Projects Group RIPE NCC

1 0

Re: [db-wg] Proxy abuse
by Thor Kottelin 30 Nov '03

30 Nov '03

> db-wg-request(a)ripe.net wrote: > From: "CMC" <icaliber(a)voicenet.com> > People using proxies on IRC is getting out of hand. On the Undernet as > example, proxy users can abuse a chat channel; be properly banned and > then return with their real hostmasks... > > I realize that the above statement is very general, however if any people > who are channel operators on any IRC chat network have been experiencing > problems with proxies, is there any solutions that the membership can > offer? Channel modes +ikm +s. Bans; if you run out of space, use dynamic, bot-controlled ban lists. On the server level, proxy checks on connect, and K: lines for the worst offenders. (This isn't at all on topic for db-wg, so follow-ups should go elsewhere. Apologies to everyone.) Thor -- http://thorweb.anta.net/

1 0