Lines Matching refs:Rule
62 As a rule, the information is statistics or some time values.
116 \item \verb|rule| --- rule in routing policy database
128 As a rule, it is possible to \verb|add|, \verb|delete| and
165 and exits. As a rule, the error message will contain information
195 syntax errors). However, as a rule, their meaning is clear
215 \verb|ip| \verb|rule| command will fail, f.e.
217 kuznet@kaiser $ ip rule list
438 involved. As a rule, it indicates that the device needs no address
508 in dropped packets. As a rule, if the interface is overrun, it means
1119 One useful exception to this rule is the default route on non-forwarding
1153 As a rule, common routing tables contain only such routes. However,
1172 rules (see sec.\ref{IP-RULE}, p.\pageref{IP-RULE}). If such a route is selected, lookup
1203 is used. See sec.\ref{IP-RULE}, p.\pageref{IP-RULE}.
1443 in the following section (sec.\ref{IP-RULE}, p.\pageref{IP-RULE}).
1896 \section{{\tt ip rule} --- routing policy database management}
1897 \label{IP-RULE}
1899 \paragraph{Abbreviations:} \verb|rule|, \verb|ru|.
1901 \paragraph{Object:} \verb|rule|s in the routing policy database control
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\/}
1945 of each rule is applied to \{source address, destination address, incoming
1950 continues on the next rule.
1972 Rule 0 is special. It cannot be deleted or overridden.
1978 routes. This rule may be deleted and/or overridden with other
1985 This rule may also be deleted.
1996 \paragraph{Rule attributes:} Each RPDB entry has additional
1997 attributes. F.e.\ each rule has a pointer to some routing
2005 \paragraph{Rule types:} The RPDB may contain rules of the following
2008 \item \verb|unicast| --- the rule prescribes to return the route found
2009 in the routing table referenced by the rule.
2010 \item \verb|blackhole| --- the rule prescribes to silently drop the packet.
2011 \item \verb|unreachable| --- the rule prescribes to generate a ``Network
2013 \item \verb|prohibit| --- the rule prescribes to generate
2015 \item \verb|nat| --- the rule prescribes to translate the source address
2024 \subsection{{\tt ip rule add} --- insert a new rule\\
2025 {\tt ip rule delete} --- delete a rule}
2026 \label{IP-RULE-ADD}
2036 --- the type of this rule. The list of valid types was given in the previous
2050 the rule only matches packets originating from this host. This means that you
2064 --- the priority of this rule. Each rule should have an explicitly
2067 Really, for historical reasons \verb|ip rule add| does not require a
2070 If the user creates a rule with a priority value that
2072 the new rule before all old rules of the same priority.
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
2120 \item Delete the unused default rule:
2129 \subsection{{\tt ip rule show} --- list rules}
2130 \label{IP-RULE-SHOW}
2152 In the first column is the rule priority value followed
2154 with the same keyword that was used to create the rule.
2159 If the rule does NAT (f.e.\ rule \#320), it is shown by the keyword
2582 with routing policy rules, see sec.~\ref{IP-RULE}, p.\pageref{IP-RULE}.
2589 \item If the rule has a source realm, the source realm of the packet is set to it.
2590 If the destination realm was not inherited from the route and the rule has a destination realm,
2869 policy rule (sec.\ref{IP-RULE-ADD}, p.\pageref{IP-RULE-ADD}):
2871 ip rule add prio 320 from 193.233.7.83 nat 192.203.80.144
2873 This rule says that the source address 193.233.7.83
2892 example from sec.\ref{IP-RULE-SHOW} (p.\pageref{IP-RULE-SHOW}).
2911 In this case you may replace rule \#320 with:
