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\/}
1362 --- the routing protocol identifier of this route.
1364 \verb|/etc/iproute2/rt_protos|. If the routing protocol ID is
1374 If a routing daemon starts, it will purge all of them.
1376 to override dynamic routing. Routing daemon will respect them
1381 to assign (or not to assign) protocol tags. At least, routing
1481 \paragraph{Description:} the command displays the contents of the routing tables
1492 than \verb|PREFIX|. F.e.\ \verb|root 0/0| selects the entire routing table.
1513 \item \verb|cache| --- dump the routing cache.
1571 To count the size of the routing cache, we have to use the \verb|-o| option
1680 \subsection{{\tt ip route flush} --- flush routing tables}
1689 as the arguments of \verb|ip route show|, but routing tables are not
1691 dumps all the IP main routing table but \verb|flush| prints the helper page.
1697 of rounds made to flush the routing table. If the option is given
1702 gatewayed routes from the main table (f.e.\ after a routing daemon crash).
1740 The third example flushes BGP routing tables after a \verb|gated|
1790 If policy routing is used, it may be a different route.
1837 (it is assumed that a multicast routing daemon is running.
1885 We may retry \verb|ip route get| to see what we have in the routing
1896 \section{{\tt ip rule} --- routing policy database management}
1901 \paragraph{Object:} \verb|rule|s in the routing policy database control
1904 Classic routing algorithms used in the Internet make routing decisions
1907 routing algorithms and their modifications can be found in~\cite{RFC1812}.
1912 This task is called ``policy routing''.
1915 ``policy routing'' $\neq$ ``routing policy''.
1917 \noindent ``policy routing'' $=$ ``cunning routing''.
1919 \noindent ``routing policy'' $=$ ``routing tactics'' or ``routing plan''.
1922 To solve this task, the conventional destination based routing table, ordered
1923 according to the longest match rule, is replaced with a ``routing policy
1943 Each policy routing rule consists of a {\em selector\/} and an {\em action\/}
1956 lookups in destination-based routing tables and selecting
1959 when a second level routing table contains a single default route.
1967 \item Priority: 0, Selector: match anything, Action: lookup routing
1969 The \verb|local| table is a special routing table containing
1975 \item Priority: 32766, Selector: match anything, Action: lookup routing
1977 The \verb|main| table is the normal routing table containing all non-policy
1981 \item Priority: 32767, Selector: match anything, Action: lookup routing
1989 Do not confuse routing tables with rules: rules point to routing tables,
1990 several rules may refer to one routing table and some routing tables
1997 attributes. F.e.\ each rule has a pointer to some routing
2001 These values do not override those contained in the routing tables. They
2009 in the routing table referenced by the rule.
2051 may create separate routing tables for forwarded and local packets and,
2081 --- the routing table identifier to lookup if the rule selector matches.
2085 --- Realms to select if the rule matched and the routing table lookup
2103 a script finishes a batch of updates, it flushes the routing cache
2109 according to routing table \verb|inr.ruhep|:
2156 The keyword \verb|lookup| is followed by a routing table identifier,
2271 \section{{\tt ip mroute} --- multicast routing cache management}
2276 \paragraph{Object:} \verb|mroute| objects are multicast routing cache
2280 Due to the limitations of the current interface to the multicast routing
2322 Each line shows one (S,G) entry in the multicast routing cache,
2326 it means that the routing daemon still hasn't resolved this entry.
2328 by spaces. If a multicast routing entry is created with non-trivial
2541 On routers using OSPF ASE or, especially, the BGP protocol, routing
2548 One approach to propagating the policy from routing protocols
2551 that dedicated routers all have the RIB (Routing Information Base)
2552 close to the forwarding engine, so policy routing rules can
2571 this identification is made by a routing daemon, but static routes
2580 To facilitate the construction (f.e.\ in case the routing
2582 with routing policy rules, see sec.~\ref{IP-RULE}, p.\pageref{IP-RULE}.
2648 Configuration Guide: Configuring Policy-Based Routing'',\\
2653 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2656 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2706 \item Otherwise, IP routing tables can contain an explicit source
2724 in routing tables instead (the \verb|scope| parameter to the \verb|ip route| command,
2799 to be used to facilitate policy routing by rewriting addresses
2800 to other routing domains or to help while renumbering sites
2901 contain a route to the destination (which means that the routing
2928 directory ftp://ftp.inr.ac.ru/ip-routing/:
