Home | History | Annotate | Download | only in doc

Lines Matching full:destination

1083 bits of its destination address are equal to the route prefix at least
1145 the preferred source address when communicating with this destination).
1222 --- the destination prefix of the route. If \verb|TYPE| is omitted,
1278 --- the MTU along the path to the destination. If the modifier \verb|lock| is
1318 If the path to these destination is asymmetric, this guess may be wrong.
1323 --- \threeonly Maximal reordering on the path to this destination.
1329 --- [2.5.74+ only] Maximum number of hops on the path to this destination.
1335 this destination. Actual window size is this value multiplied by the
1342 + this destination. The actual window size is this value multiplied
1406 route to the same destination exists. Its opposite case is \verb|append|,
1627 \item \verb|mc| --- the destination is multicast.
1629 \item \verb|brd| --- the destination is broadcast.
1644 \item \verb|dst-nat| --- the destination address requires translation.
1760 \paragraph{Description:} this command gets a single route to a destination
1767 --- the destination address.
1798 to output packets towards the requested destination.
1799 This is equivalent to pinging the destination
1857 gatewayed route for a destination which is really directly connected:
1883 better path to the destination and sent us an ICMP redirect message.
1904 based only on the destination address of packets (and in theory,
1909 on destination addresses, but also on other packet fields: source address,
1921 To solve this task, the conventional destination based routing table, ordered
1932 \item packet destination address.
1944 of each rule is applied to \{source address, destination address, incoming
1955 lookups in destination-based routing tables and selecting
2044 --- select the destination prefix to match.
2296 --- the prefix selecting the destination multicast addresses to list.
2543 want to distinguish the packets not only by their destination, but
2567 classification both by source and destination becomes quite manageable.
2584 and destination realm, using the following algorithm:
2587 \item If the route has a realm, the destination realm of the packet is set to it.
2589 If the destination realm was not inherited from the route and the rule has a destination realm,
2626 summarizing traffic not only by source or destination, but
2627 by any pair of source and destination realms.
2706 address hint for this destination. The hint is set with the \verb|src| parameter
2716 with the same scope as the destination.
2719 than the scope of the destination but it prefers addresses
2721 to the destination. Unlike IPv6, the scopes of IPv4 destinations
2729 \item Otherwise, if the scope of the destination is \verb|link| or \verb|host|,
2748 the route to the requested destination does {\em not\/} go back via the same
2756 NDISC queries. It means that proxy NDISC is possible only on a per destination
2784 to the destination goes back via the interface from which the solicitation
2900 contain a route to the destination (which means that the routing