Lines Matching refs:routing

150 \item \verb|route| --- routing table entry
151 \item \verb|rule| --- rule in routing policy database
153 \item \verb|mroute| --- multicast routing cache entry
1107 \section{{\tt ip route} --- routing table management}
1112 \paragraph{Object:} \verb|route| entries in the kernel routing tables keep
1168 in this sequence. Instead, the routing table in the kernel is kept
1171 routing algorithm implemented in the kernel, we can summarize
1174 the route in the routing table.
1176 \paragraph{Route attributes:} Each route key refers to a routing
1188 As a rule, common routing tables contain only such routes. However,
1209 Without policy routing it is equivalent to the absence of the route in the routing
1221 \item \verb|multicast| --- a special type used for multicast routing.
1222 It is not present in normal routing tables.
1225 \paragraph{Route tables:} Linux-2.2 can pack routes into several routing
1237 The multiple routing tables enter the game when {\em policy routing\/}
1404 --- the routing protocol identifier of this route.
1406 \verb|/etc/iproute2/rt_protos|. If the routing protocol ID is
1416 If a routing daemon starts, it will purge all of them.
1418 to override dynamic routing. Routing daemon will respect them
1423 to assign (or not to assign) protocol tags. At least, routing
1526 \paragraph{Description:} the command displays the contents of the routing tables
1537 than \verb|PREFIX|. F.e.\ \verb|root 0/0| selects the entire routing table.
1558   \item \verb|cache| --- dump the routing cache.
1616 To count the size of the routing cache, we have to use the \verb|-o| option
1724 \subsection{{\tt ip route save} -- save routing tables}
1727 \paragraph{Description:} this command saves the contents of the routing
1743 \subsection{{\tt ip route restore} -- restore routing tables}
1746 \paragraph{Description:} this command restores the contents of the routing
1760 \subsection{{\tt ip route flush} --- flush routing tables}
1769 as the arguments of \verb|ip route show|, but routing tables are not
1771 dumps all the IP main routing table but \verb|flush| prints the helper page.
1777 of rounds made to flush the routing table. If the option is given
1782 gatewayed routes from the main table (f.e.\ after a routing daemon crash).
1820 The third example flushes BGP routing tables after a \verb|gated|
1870 If policy routing is used, it may be a different route.
1917 (it is assumed that a multicast routing daemon is running.
1965 We may retry \verb|ip route get| to see what we have in the routing
1976 \section{{\tt ip rule} --- routing policy database management}
1981 \paragraph{Object:} \verb|rule|s in the routing policy database control
1984 Classic routing algorithms used in the Internet make routing decisions
1987 routing algorithms and their modifications can be found in~\cite{RFC1812}.
1992 This task is called ``policy routing''.
1995   ``policy routing'' $\neq$ ``routing policy''.
1997 \noindent	``policy routing'' $=$ ``cunning routing''.
1999 \noindent	``routing policy'' $=$ ``routing tactics'' or ``routing plan''.
2002 To solve this task, the conventional destination based routing table, ordered
2003 according to the longest match rule, is replaced with a ``routing policy
2023 Each policy routing rule consists of a {\em selector\/} and an {\em action\/}
2036 lookups in destination-based routing tables and selecting
2039 when a second level routing table contains a single default route.
2047 \item Priority: 0, Selector: match anything, Action: lookup routing
2049 The \verb|local| table is a special routing table containing
2055 \item Priority: 32766, Selector: match anything, Action: lookup routing
2057 The \verb|main| table is the normal routing table containing all non-policy
2061 \item Priority: 32767, Selector: match anything, Action: lookup routing
2069 Do not confuse routing tables with rules: rules point to routing tables,
2070 several rules may refer to one routing table and some routing tables
2077 attributes. F.e.\ each rule has a pointer to some routing
2081 These values do not override those contained in the routing tables. They
2089 in the routing table referenced by the rule.
2131 may create separate routing tables for forwarded and local packets and,
2161 --- the routing table identifier to lookup if the rule selector matches.
2165 --- Realms to select if the rule matched and the routing table lookup
2183 a script finishes a batch of updates, it flushes the routing cache
2189 according to routing table \verb|inr.ruhep|:
2236 The keyword \verb|lookup| is followed by a routing table identifier,
2387 \section{{\tt ip mroute} --- multicast routing cache management}
2392 \paragraph{Object:} \verb|mroute| objects are multicast routing cache
2396 Due to the limitations of the current interface to the multicast routing
2438 Each line shows one (S,G) entry in the multicast routing cache,
2442 it means that the routing daemon still hasn't resolved this entry.
2444 by spaces. If a multicast routing entry is created with non-trivial
2659 On routers using OSPF ASE or, especially, the BGP protocol, routing
2666 One approach to propagating the policy from routing protocols
2670 close to the forwarding engine, so policy routing rules can
2689 this identification is made by a routing daemon, but static routes
2698 To facilitate the construction (f.e.\ in case the routing
2700 with routing policy rules, see sec.~\ref{IP-RULE}, p.\pageref{IP-RULE}.
2771 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2774 In: {\tt ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz}.
2824 \item Otherwise, IP routing tables can contain an explicit source
2842 in routing tables instead (the \verb|scope| parameter to the \verb|ip route| command,
2917 to be used to facilitate policy routing by rewriting addresses
2918 to other routing domains or to help while renumbering sites
3019 contain a route to the destination (which means that the routing
3046 directory ftp://ftp.inr.ac.ru/ip-routing/: