Lines Matching refs:tables
832 \section{{\tt ip neighbour} --- neighbour/arp tables management}
839 Neighbour entries are organized into tables. The IPv4 neighbour table
929 The deleted neighbour entry will not disappear from the tables
946 \paragraph{Description:}This commands displays neighbour tables.
1045 \paragraph{Description:}This command flushes neighbour tables, selecting
1077 \paragraph{Object:} \verb|route| entries in the kernel routing tables keep
1153 As a rule, common routing tables contain only such routes. However,
1187 It is not present in normal routing tables.
1190 \paragraph{Route tables:} Linux-2.2 can pack routes into several routing
1191 tables identified by a number in the range from 1 to 255 or by
1202 The multiple routing tables enter the game when {\em policy routing\/}
1480 \paragraph{Description:} the command displays the contents of the routing tables
1511 \item \verb|all| --- list all of the tables.
1678 \subsection{{\tt ip route save} -- save routing tables}
1682 tables or the route(s) selected by some criteria to standard output.
1697 \subsection{{\tt ip route restore} -- restore routing tables}
1701 tables according to a data stream as provided by \verb|ip route save| via
1703 Any routes in the input stream that already exist in the tables are ignored.
1714 \subsection{{\tt ip route flush} --- flush routing tables}
1723 as the arguments of \verb|ip route show|, but routing tables are not
1774 The third example flushes BGP routing tables after a \verb|gated|
1920 tables now:
1990 lookups in destination-based routing tables and selecting
1991 a route from these tables according to the classic longest match algorithm.
1994 Recall that Linux-2.2 supports multiple tables
2023 Do not confuse routing tables with rules: rules point to routing tables,
2024 several rules may refer to one routing table and some routing tables
2035 These values do not override those contained in the routing tables. They
2085 may create separate routing tables for forwarded and local packets and,
2576 tables may be huge. If we want to classify or to account for the packets
2740 \item Otherwise, IP routing tables can contain an explicit source
2758 in routing tables instead (the \verb|scope| parameter to the \verb|ip route| command,
