From 7d837aa014a78bce2b329cc9f56e8dc799d456e8 Mon Sep 17 00:00:00 2001 From: Ondrej Zajicek Date: Thu, 15 Mar 2012 12:43:47 +0100 Subject: [PATCH] Fixes documentation - default pipe mode. Thanks to Benjamin Cama for the bugreport. --- doc/bird.sgml | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/doc/bird.sgml b/doc/bird.sgml index b8dabf47..f06e21c9 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -2085,17 +2085,18 @@ and vice versa, depending on what's allowed by the filters. Export filters contr of routes from the primary table to the secondary one, import filters control the opposite direction. -

The Pipe protocol may work in the opaque mode or in the transparent -mode. In the opaque mode, the Pipe protocol retransmits optimal route +

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. The opaque mode is a default mode. - -

In 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 mode can be set by +specific route attributes. This mode is mainly for compatibility, it +is not suggested for new configs. The mode can be changed by The primary use of multiple routing tables and the Pipe protocol is for policy routing,