Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

IRRd-Discuss


Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

database inconsistencies?

  • From: Jens-S. Voeckler
  • Date: Thu Oct 21 02:26:12 1999

Hi,

I am using a local irrd to mirror the RA provided databases:

   IRRd> show database
   Listening on port 43 (fd=18)
   Memory-only indexing
   RIPE181 Syntax

   Database    Size (kb)    Rt Obj   AutNum Obj   Serial #
   ---------    --------     ------   ---------   ---------
    ans            4964.4      10561       26        37592
    canet          1095.5       9629       59        0
    mci            7516.6      47656      562        0
    radb          12948.8      55031     1994        75127
    ripe           5939.2      21165     2612        6530703

   ans
      Mirroring 198.108.0.11:43 (Next in 21:40:30)
      Never mirrored
      Next dbclean in 45:15:57
   canet
      Last loaded 04:32:20 10/21/99
   mci
      Last loaded 04:32:23 10/21/99
   radb
      Mirroring 198.108.0.11:43 (Next in 21:40:28)
      Never mirrored
      Next dbclean in 44:31:52
   ripe
      Mirroring 198.108.0.11:43 (Next in 21:39:47)
      Never mirrored
      Next dbclean in 45:13:46

Since my Squid web cache software uses AS based ACLs and request routing,
I rely on the correct information in the databases. Strangely enough,
there seems to be a mixup concerning 145.253.0.0/16..18. Squid reports
(verified by querying RA):

> ]> 
> ]>     145.253.0.0/18       3211
> ]>     145.253.0.0/16       1275

The AS1275 NOC claims that 145.253.0.0/16 does not belong to AS1275. RIPE
does report the network correctly to belong to AS3211. But when querying
RA (and my local mirror), it also claims that CW says the network belongs
to AS1275, even though it falls into the RIPE domain:

   $ whois -h whois.ripe.net 145.253.67.0
   [...]
   route:       145.253.0.0/16
   descr:       ARCOR-IP
   origin:      AS3209
   [...]

   $ whois -h whois.ripe.net 145.253.0.0
   [...]
   route:       145.253.0.0/18
   descr:       ARCOR-IP
   origin:      AS3211
   [...]

   $ whois -h whois.ra.net. 145.253.0.0
   [...]
   route:          145.253.0.0/18
   descr:          ARCOR-IP
   origin:         AS3211
   notify:         markus.hies@arcor.net
   mnt-by:         ARCOR-MNT
   changed:        markus.hies@ripe.net 19980806
   changed:        markus.hies@arcor.net 19981013
   source:         RIPE

   route:          145.253.0.0/16
   descr:          ARCOR-IP
   origin:         AS1275  <-- this is the start of wrong information
   mnt-by:         DFN-MNT
   changed:        poldi@dfn.de 980422
   source:         CW

Who does resolve such inconsistencies?

Yours
Dipl.-Ing. Jens-S. Vöckler (voeckler@rvs.uni-hannover.de)
Institute for Computer Networks and Distributed Systems
University of Hanover, Germany; +49 511 762 4726





[an error occurred while processing this directive]