From: Ondrej Zajicek (work) Date: Tue, 21 Aug 2018 13:24:55 +0000 (+0200) Subject: DOC: Remove pipe mode reference X-Git-Tag: v2.0.3~58 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=765f400f6b7ac054ddb4fcc4f5bec58f94d1bdd4;p=thirdparty%2Fbird.git DOC: Remove pipe mode reference Pipe mode was removed in 2.0, remove reference to it in the documentation. Thanks to Piotr Wydrych for the bugreport. --- diff --git a/doc/bird.sgml b/doc/bird.sgml index 93b701d37..0057d2c50 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -3656,18 +3656,9 @@ the filters. Export filters control export of routes from the primary table to the secondary one, import filters control the opposite direction. Both tables must be of the same nettype. -

The Pipe protocol may work in the transparent mode mode or in the opaque -mode. In the transparent mode, the Pipe protocol retransmits all routes from -one table to the other table, retaining their original source and attributes. -If import and export filters are set to accept, then both tables would have -the same content. The transparent mode is the default mode. - -

In the opaque mode, the Pipe protocol retransmits optimal route from one -table to the other table in a similar way like other protocols send and receive -routes. Retransmitted route will have the source set to the Pipe protocol, which -may limit access to protocol specific route attributes. This mode is mainly for -compatibility, it is not suggested for new configs. The mode can be changed by -The Pipe protocol retransmits all routes from one table to the other table, +retaining their original source and attributes. If import and export filters +are set to accept, then both tables would have the same content.

The primary use of multiple routing tables and the Pipe protocol is for policy routing, where handling of a single packet doesn't depend only on its