From 1ca7665fa4a9858a6d4c591ccff5b61e5e6aed13 Mon Sep 17 00:00:00 2001 From: "Ondrej Zajicek (work)" Date: Tue, 19 May 2020 02:50:47 +0200 Subject: Nest: Allow key id 0 There is nothing in RFCs specifying that id 0 is not allowed. Some implementations does not support it, while some other use key id 0 by default. We allow it but start with key id 1 by default. Thanks to Kenth Eriksson for the bugreport. --- doc/bird.sgml | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'doc/bird.sgml') diff --git a/doc/bird.sgml b/doc/bird.sgml index 33f6418f..401b4035 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -783,11 +783,12 @@ agreement"). - ID of the password, (1-255). If it is not used, BIRD will choose ID based - on an order of the password item in the interface. For example, second - password item in one interface will have default ID 2. ID is used by - some routing protocols to identify which password was used to - authenticate protocol packets. + ID of the password, (0-255). If it is not specified, BIRD will choose ID + based on an order of the password item in the interface, starting from + 1. For example, second password item in one interface will have default + ID 2. ID 0 is allowed by BIRD, but some other implementations may not + allow it. ID is used by some routing protocols to identify which + password was used to authenticate protocol packets.