Re: fancy route objects

[Carol Orange <Carol.Orange@localhost]

Dear Gabor, 
 
"Gabor Kiss \(Bitman\)" writes:

>> Dear Colleagues,
>> 
>> Are there these route objects correct (is this some very new feature?)
>> or they come from some software bug?

They are from a software bug, reported to the list in August. The
message which contains instructions on how to fix and prevent this 
is included below. 

>> Three independent user can't get mad the same time.

You underestimate users ;-)

>> Note: these objects cannot be queried. I've browsed the mirrored DB file.
>> 
>> Gabor

Sorry for the inconvenience. We will see to a fix as soon as possible.

Carol Orange
RIPE NCC
 
>> *rt: 127.255.255.255/24
>> *de: TAT GmbH Systeme der grafische Datenverarbeit
>> *or: AS2856
>> *mb: BTNET-MNT
>> *ch: Paul.Dyke@localhost 970916
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/16
>> *de: upstream provider: Swisscom (formerly Unisource Business Networks)
>> *or: AS3303
>> *mb: CH-UNISOURCE-MNT
>> *ch: bridge@localhost 971017
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/24
>> *de: upstream provider: Swisscom (formerly Unisource Business Networks)
>> *or: AS3303
>> *mb: CH-UNISOURCE-MNT
>> *ch: bridge@localhost 971017
>> *so: RIPE
>> 
>> *rt: 127.255.255.255/23
>> *de: HU-CEU
>> *or: AS2012
>> *mb: AS2012-MNT
>> *ch: gaga@localhost 971027
>> *so: RIPE

-----------------------------------------------------------------------
From ripe-dbm@localhost Fri Aug 22 21:20:52 1997
Received: from office.ripe.net by ncc.ripe.net with SMTP
	id AA13058 (5.65a/NCC-2.41); Fri, 22 Aug 1997 21:20:51 +0200
Message-Id: <9708221920.AA13058@localhost>, local-ir@localhost
Subject: Bug in database software.
Cc: woeber@localhost, panigl@localhost, orange@localhost
From: RIPE Database Administration ripe-dbm@localhost
X-Organization: RIPE Network Coordination Centre
X-Phone: +31 20 535 4444
X-Fax: +31 20 535 4445
Date: Fri, 22 Aug 1997 21:20:51 +0200
Sender: ripe-dbm@localhost


Dear Colleagues,

This message is to report a bug in the database software.  

If you send in an update of a route object in the classful
net notation (e.g. 193.0.0.0) instead of the classless
representation, you will get a warning message indicating
that the route was rewritten to 127.255.255.255/24.
You should find that you can lookup the original 
route object in the database.  You should also find
that you cannot lookup the new spurious route object,
127.255.255.255\24.

You should do the following:

(1) update your original route object using the
classless notation;

(2) delete the 127.255.255.255\24 object; you will
find it in the acknowledgement you received from the
first update.

We will fix this problem as soon as possible.

If you have anymore questions, please contact
ripe-dbm@localhost.

Regards,

Ambrose Magee
____________________________
RIPE Database Administration.