This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] RIPE DB Route Object fails creation
- Previous message (by thread): [db-wg] RIPE DB Route Object fails creation
- Next message (by thread): [db-wg] RIPE DB Route Object fails creation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tom Hill
tom at ninjabadger.net
Thu Jun 11 14:28:16 CEST 2020
Hello, On 11/06/2020 03:26, ripedenis--- via db-wg wrote: > If there is an existing, exact matching ROUTE object the creation of the > new ROUTE object must be authorised by the existing object. There is a > flow chart here explaining the sequence of checks: > https://www.ripe.net/support/training/material/bgp-operations-and-security-training-course/route-object-creation-flowchart.pdf This comes up a lot, particularly with PI space. It confused the hell out of me when I first had to decipher that flow chart, and I realised recently that I hadn't looked at it for long enough that it had once again fallen out of my head. > ***Error: Authorisation for [route] 194.76.156.0/22AS20676 failed > using "mnt-by:" > not authenticated by: PLUSNET-NOC Could we reduce the confusion, and/or spread some more clue, by being more specific with this error? e.g. Authorisation for [blah] failed using "mnt-by:" - matching route object already exists - not authenticated by: PLUSNET-NOC Regards, -- Tom
- Previous message (by thread): [db-wg] RIPE DB Route Object fails creation
- Next message (by thread): [db-wg] RIPE DB Route Object fails creation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]