About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE NCC Mail Archives
     
Mailing Lists:
RIPE NCC Navigation Ends
Link to NCC Lists Archive NCC Lists Archive
Link to RIPE Lists Archive RIPE Lists Archive
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: auth failures

  • To: Frank Bohnsack < >
  • From: Engin Gunduz < >
  • Date: Wed, 31 Jan 2001 11:18:50 +0100 (CET)

Hi Frank,

This was because of new authorisation scheme, from
rps-auth (RFC2725). According to this, when creating an
aut-num object, an as-block object must exist with a range
which includes the aut-num to-be-created, and the creation must
be authorised by the maintainer mentioned in the "mnt-lower"
attribute of that as-block.

In this case, an as-block object which includes AS1270
didn't exist in our test DB, and your creation request denied.

Now, we have created "as-block:   AS1200 - AS1300" with
a "mnt-lower:  AS-BLOCK-MNT" attribute, the auth of AS-BLOCK-MNT
being NONE. So, you must be able create AS1270 now.



On Wed, 31 Jan 2001, Frank Bohnsack wrote:

> Dear RIPE DB colleagues,
>
> I tried to create a new aut-num object mnt-by UUNETDE-MNT.
> The auth attribute is set to: auth: MAIL-FROM .*@localhost\.uu\.net and
> my sender address is fb@localhost, but your robot doesn't execute
> my requests ;-(
>
> > New FAILED: [aut-num] AS1270
> > Auth failed
>
> Furthermore the mnt-upd email looks like below, i feel the header wasn't
> duly completed ?!?!


Ah, right. We'll fix this ASAP.

Best regards,

Engin Gunduz
RIPE NCC Database Group


>
> cheers
> Frank
>
> On 31-Jan-2001 bit-bucket@localhost wrote:
>  >
>  > Dear Maintainer,
>  >
>  > This is to notify you that some objects in which you are mentioned as
>  > a maintainer were requested to be changed, but *failed* the proper
>  > authorisation for any of the mentioned maintainers.
>  > Please contact the sender of these changes about changes that need
>  > to be made to the following objects.
>  >
>  >
>  >
>  > The mail message causing these failures had the following mail headers:
>  >
>  > - From:    $FROM
>  > - Cc:      $CC
>  > - Subject: $SUBJECT
>  > - Date:    $MDATE
>  > - Msg-Id:  $MSGID
>  >
>  > RIPE Database Maintainer Forwarding Department
>  >
>  > ----
>  > ADDITION REQUESTED FOR:
>  >
>  > aut-num:      AS1270
>  > as-name:      UUNET-DE
>  > descr:        UUNET Germany
>  > import:       from AS1
>  >               action pref=100;
>  >               accept AS1
>  > export:       to AS1
>  >               announce ANY
>  > admin-c:      FB-RIPE
>  > tech-c:       FB-RIPE
>  > notify:       fb@localhost
>  > mnt-by:       UUNETDE-MNT
>  > changed:      fb@localhost 20010131
>  > source:       RIPE
>  >
>
> --
> Frank Bohnsack                       email  fb@localhost
> UUNET, A Worldcom Company            phone  +49 (0)231 972-1495
> EMEA Access & Backbone Networks      fax    +49 (0)231 972-1188
> Team Dortmund                        web    www.de.uu.net
>





  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | © RIPE NCC. All rights reserved.
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages