From d8c7d9e8846f025e42227c64e992a3a52ca7dfb4 Mon Sep 17 00:00:00 2001 From: Ondrej Filip Date: Sun, 20 Feb 2005 04:27:56 +0000 Subject: Since now I can also use 'dead interval', not just 'dead counter'. --- doc/bird.conf.example | 1 + doc/bird.sgml | 7 +++++++ 2 files changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/bird.conf.example b/doc/bird.conf.example index 704abef..8260c02 100644 --- a/doc/bird.conf.example +++ b/doc/bird.conf.example @@ -122,6 +122,7 @@ protocol static { # interface "arc0" { # type nonbroadcast; # poll 14; +# dead 75; # neighbors { # 10.1.1.2 eligible; # 10.1.1.4; diff --git a/doc/bird.sgml b/doc/bird.sgml index 79d7e96..3c23309 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -1024,6 +1024,7 @@ protocol ospf <name> { priority <num>; wait <num>; dead count <num>; + dead <num>; type [broadcast|nonbroadcast|pointopoint]; strict nonbroadcast <switch>; authentication [none|simple]; @@ -1048,6 +1049,7 @@ protocol ospf <name> { retransmit <num>; wait <num>; dead count <num>; + dead <num>; authentication [none|simple]; password "<text>"; }; @@ -1126,6 +1128,11 @@ protocol ospf <name> { When the router does not receive any messages from a neighbor in dead num + When the router does not receive any messages from a neighbor in + type broadcast BIRD detects a type of a connected network automatically, but sometimes it's convenient to force use of a different type manually. -- cgit v1.2.3