Home | History | Annotate | Download | only in doc

Lines Matching refs:routing

115 \item \verb|route| --- routing table entry
116 \item \verb|rule| --- rule in routing policy database
118 \item \verb|mroute| --- multicast routing cache entry
1072 \section{{\tt ip route} --- routing table management}
1077 \paragraph{Object:} \verb|route| entries in the kernel routing tables keep
1133 in this sequence. Instead, the routing table in the kernel is kept
1136 routing algorithm implemented in the kernel, we can summarize
1139 the route in the routing table.
1141 \paragraph{Route attributes:} Each route key refers to a routing
1153 As a rule, common routing tables contain only such routes. However,
1174 Without policy routing it is equivalent to the absence of the route in the routing
1186 \item \verb|multicast| --- a special type used for multicast routing.
1187 It is not present in normal routing tables.
1190 \paragraph{Route tables:} Linux-2.2 can pack routes into several routing
1202 The multiple routing tables enter the game when {\em policy routing\/}
1369 --- the routing protocol identifier of this route.
1371 \verb|/etc/iproute2/rt_protos|. If the routing protocol ID is
1381 If a routing daemon starts, it will purge all of them.
1383 to override dynamic routing. Routing daemon will respect them
1388 to assign (or not to assign) protocol tags. At least, routing
1480 \paragraph{Description:} the command displays the contents of the routing tables
1491 than \verb|PREFIX|. F.e.\ \verb|root 0/0| selects the entire routing table.
1512 \item \verb|cache| --- dump the routing cache.
1570 To count the size of the routing cache, we have to use the \verb|-o| option
1679 \subsection{{\tt ip route flush} --- flush routing tables}
1688 as the arguments of \verb|ip route show|, but routing tables are not
1690 dumps all the IP main routing table but \verb|flush| prints the helper page.
1696 of rounds made to flush the routing table. If the option is given
1701 gatewayed routes from the main table (f.e.\ after a routing daemon crash).
1739 The third example flushes BGP routing tables after a \verb|gated|
1789 If policy routing is used, it may be a different route.
1836 (it is assumed that a multicast routing daemon is running.
1884 We may retry \verb|ip route get| to see what we have in the routing
1895 \section{{\tt ip rule} --- routing policy database management}
1900 \paragraph{Object:} \verb|rule|s in the routing policy database control
1903 Classic routing algorithms used in the Internet make routing decisions
1906 routing algorithms and their modifications can be found in~\cite{RFC1812}.
1911 This task is called ``policy routing''.
1914 ``policy routing'' $\neq$ ``routing policy''.
1916 \noindent ``policy routing'' $=$ ``cunning routing''.
1918 \noindent ``routing policy'' $=$ ``routing tactics'' or ``routing plan''.
1921 To solve this task, the conventional destination based routing table, ordered
1922 according to the longest match rule, is replaced with a ``routing policy
1942 Each policy routing rule consists of a {\em selector\/} and an {\em action\/}
1955 lookups in destination-based routing tables and selecting
1958 when a second level routing table contains a single default route.
1966 \item Priority: 0, Selector: match anything, Action: lookup routing
1968 The \verb|local| table is a special routing table containing
1974 \item Priority: 32766, Selector: match anything, Action: lookup routing
1976 The \verb|main| table is the normal routing table containing all non-policy
1980 \item Priority: 32767, Selector: match anything, Action: lookup routing
1988 Do not confuse routing tables with rules: rules point to routing tables,
1989 several rules may refer to one routing table and some routing tables
1996 attributes. F.e.\ each rule has a pointer to some routing
2000 These values do not override those contained in the routing tables. They
2008 in the routing table referenced by the rule.
2050 may create separate routing tables for forwarded and local packets and,
2080 --- the routing table identifier to lookup if the rule selector matches.
2084 --- Realms to select if the rule matched and the routing table lookup
2102 a script finishes a batch of updates, it flushes the routing cache
2108 according to routing table \verb|inr.ruhep|:
2155 The keyword \verb|lookup| is followed by a routing table identifier,
2270 \section{{\tt ip mroute} --- multicast routing cache management}
2275 \paragraph{Object:} \verb|mroute| objects are multicast routing cache
2279 Due to the limitations of the current interface to the multicast routing
2321 Each line shows one (S,G) entry in the multicast routing cache,
2325 it means that the routing daemon still hasn't resolved this entry.
2327 by spaces. If a multicast routing entry is created with non-trivial
2540 On routers using OSPF ASE or, especially, the BGP protocol, routing
2547 One approach to propagating the policy from routing protocols
2550 that dedicated routers all have the RIB (Routing Information Base)
2551 close to the forwarding engine, so policy routing rules can
2570 this identification is made by a routing daemon, but static routes
2579 To facilitate the construction (f.e.\ in case the routing
2581 with routing policy rules, see sec.~\ref{IP-RULE}, p.\pageref{IP-RULE}.
2647 Configuration Guide: Configuring Policy-Based Routing'',\\
2652 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2655 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2705 \item Otherwise, IP routing tables can contain an explicit source
2723 in routing tables instead (the \verb|scope| parameter to the \verb|ip route| command,
2798 to be used to facilitate policy routing by rewriting addresses
2799 to other routing domains or to help while renumbering sites
2900 contain a route to the destination (which means that the routing
2927 directory ftp://ftp.inr.ac.ru/ip-routing/: