Commit 7d837aa0 authored by Ondřej Zajíček's avatar Ondřej Zajíček

Fixes documentation - default pipe mode.

Thanks to Benjamin Cama for the bugreport.
parent e2bf812f
......@@ -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.
<p>The Pipe protocol may work in the opaque mode or in the transparent
mode. In the opaque mode, the Pipe protocol retransmits optimal route
<p>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.
<p>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.
<p>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
<tt/mode/ option.
<p>The primary use of multiple routing tables and the Pipe protocol is for policy routing,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment