Lines Matching refs:In
36 discussion, are in the appendix.
49 begin with the character \verb|'-'| and may be used in either long or abbreviated
116 \item \verb|rule| --- rule in routing policy database
122 Again, the names of all objects may be written in full or
146 In the command descriptions below such parameters
151 but they are not recommended in scripts or when reporting bugs
153 in the document body.
164 IP address {\em et al\/}. In this case \verb|ip| prints an error message
176 The kernel returned an error to some syscall. In this case \verb|ip|
182 In this case \verb|ip| prints the error message, as it is output
189 in the system. One harmful exception is \verb|ip link| command
201 \item Netlink is not configured in the kernel. The message is:
206 \item RTNETLINK is not configured in the kernel. In this case
214 when configuring the kernel. In this case any attempt to use the
253 This operation is {\em not allowed\/} if the device is in state \verb|UP|.
386 does not queue anything and \verb|noop| means that the interface is in blackhole
389 in packets.
391 The interface flags are summarized in the angle brackets.
477 \verb|ip maddr ls| in~Sec.\ref{IP-MADDR} (p.\pageref{IP-MADDR} of this
508 in dropped packets. As a rule, if the interface is overrun, it means
509 serious problems in the kernel or that your machine is too slow
542 may have non zero values in these fields but they may be
555 for them and we do not use it in this document.
598 instead of the broadcast address. In this case, the broadcast address
611 In order to preserve compatibility with Linux-2.0 net aliases,
619 The available scopes are listed in file \verb|/etc/iproute2/rt_scopes|.
672 may be found in sec.\ref{IP-ADDR-FLUSH}, p.\pageref{IP-ADDR-FLUSH}.
758 There is a tweak in \verb|/proc/sys/net/ipv4/conf/<dev>/promote_secondaries|
762 This tweak is available in linux 2.6.15 and later.
768 In this case the output also contains information on times, when
805 in the format described in the previous subsection.
930 immediately. If it is in use it cannot be deleted until the last
937 a \verb|noarp| entry created by the kernel may result in unpredictable behaviour.
962 --- only list neighbours which are not currently in use.
966 --- only list neighbour entries in this state. \verb|NUD_STATE| takes
995 state machine can be found in~\cite{RFC-NDISC}. Here is the full list
1000 \item\verb|incomplete| --- the neighbour is in the process of resolution.
1015 The link layer address is valid in all states except for \verb|none|,
1032 and \verb|used| is a triplet of time intervals in seconds
1033 separated by slashes. In this case they show that:
1058 in the format described in the previous subsection.
1077 \paragraph{Object:} \verb|route| entries in the kernel routing tables keep
1111 impossible to maintain a bundle of such routes in this order.
1117 non-unique routes with \verb|ip| commands described in this section.
1122 In this case, Linux-2.2 makes ``dead gateway detection''~\cite{RFC1122}
1125 of the routes is not essential. However, in this case,
1133 in this sequence. Instead, the routing table in the kernel is kept
1134 in some data structure to achieve the final result
1136 routing algorithm implemented in the kernel, we can summarize
1139 the route in the routing table.
1146 These attributes are described in the following subsection.
1173 in this table is terminated pretending that no route was found.
1174 Without policy routing it is equivalent to the absence of the route in the routing
1181 in Appendix~\ref{ROUTE-NAT}, p.\pageref{ROUTE-NAT}.
1187 It is not present in normal routing tables.
1191 tables identified by a number in the range from 1 to 255 or by
1204 In this case, the table identifier effectively becomes
1260 router or, if it is a direct route installed in BSD compatibility mode,
1281 all packets will be sent without the DF bit in IPv4 case
1287 measured in bytes. It limits maximal data bursts that our TCP
1337 zero, meaning to use the values specified in~\cite{RFC2414}.
1383 f.e.\ as they are assigned in \verb|rtnetlink.h| or in \verb|rt_protos|
1391 option may be found in~\cite{IP-TUNNELS}.
1414 this will change in the future.
1443 in the following section (sec.\ref{IP-RULE}, p.\pageref{IP-RULE}).
1468 \item delete the multipath route created by the command in previous subsection
1613 see in the section on \verb|ip route get| (p.\pageref{NB-nature-of-strangeness})
1618 Cached flags are summarized in angle brackets:
1626 in an error. See attribute \verb|error| below (p.\pageref{IP-ROUTE-GET-error}).
1650 This feature disappeared in linux-2.4.
1661 senders, according to the rules described above in the subsection
1699 in the format described in the previous subsection.
1708 This option was described in the \verb|route(8)| man page borrowed
1709 from BSD, but was never implemented in Linux.
1806 \paragraph{Output format:} This command outputs routes in the same
1838 In this case, it is \verb|pimd|)
1848 deliver) the packet to local IP listeners. In this case the router
1885 We may retry \verb|ip route get| to see what we have in the routing
1901 \paragraph{Object:} \verb|rule|s in the routing policy database control
1904 Classic routing algorithms used in the Internet make routing decisions
1905 based only on the destination address of packets (and in theory,
1906 but not in practice, on the TOS field). The seminal review of classic
1907 routing algorithms and their modifications can be found in~\cite{RFC1812}.
1909 In some circumstances we want to route packets differently depending not only
1941 \verb|fwmark| is also included in the set of keys checked by rules.
1944 predicate. The RPDB is scanned in the order of increasing priority. The selector
1948 In this case, it will either give a route or failure indication
1956 lookups in destination-based routing tables and selecting
1961 managed with the \verb|ip route| command, described in the previous section.
1993 and will disappear only after all the routes contained in it are deleted.
2001 These values do not override those contained in the routing tables. They
2009 in the routing table referenced by the rule.
2017 in Appendix~\ref{ROUTE-NAT}, p.\pageref{ROUTE-NAT}.
2036 --- the type of this rule. The list of valid types was given in the previous
2074 It is mistake in design, no more. And it will be fixed one day,
2093 (selected by NAT routes) or in linux-2.2 a local host address (or even zero).
2094 In the last case the router does not translate the packets,
2095 but masquerades them to this address; this feature disappered in 2.4.
2096 More about NAT is in Appendix~\ref{ROUTE-NAT},
2152 In the first column is the rule priority value followed
2157 as it is recorded in the file \verb|/etc/iproute2/rt_tables|.
2212 One additional feature not present in the example above
2262 It is not a bug, but rather a hole in the API and intra-kernel interfaces.
2283 in the future.
2322 Each line shows one (S,G) entry in the multicast routing cache,
2330 in the \verb|oifs| list.
2350 packets in IPv4 packets and then sending them over the IP infrastructure.
2356 over IP and the \verb|ip tunnel| command can be found in~\cite{IP-TUNNELS}.
2391 \verb|N| is a number in the range 1--255. 0 is a special value
2418 The \verb|key| parameter sets the key to use in both directions.
2508 the \verb|monitor| command is the first in the command line and then
2516 listens on it and dumps state changes in the format described
2517 in previous sections.
2520 but opens the file containing RTNETLINK messages saved in binary format
2530 in a startup script, you will be able to view the full history
2549 to the forwarding engine has been proposed in~\cite{IOS-BGP-PP}.
2563 Namely, routes can be clustered together in user space, based on their
2576 to realms with all the set of policy rules implemented in \verb|gated|:
2580 To facilitate the construction (f.e.\ in case the routing
2652 ``Tunnels over IP in Linux-2.2'', \\
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}.
2683 reply. If the source is selected incorrectly, in the best case,
2685 is harmful for performance. In the worst case, when the addresses
2694 \verb|IP_PKTINFO|. In this case the kernel only checks the validity
2723 are not encoded in their addresses but are supplied
2724 in routing tables instead (the \verb|scope| parameter to the \verb|ip route| command,
2735 in the search list, so that if an address with global scope (not 127.0.0.1!)
2745 In Linux-2.2 proxy ARP on an interface may be enabled
2755 However, this approach fails in the case of IPv6 because the router
2761 in user space. However, similar functionality was present in BSD kernels
2762 and in Linux-2.0, so we have to preserve it at least to the extent that
2763 is standardized in BSD.
2766 It is replaced with the sysctl flag in Linux-2.2.
2842 only in stub networks but in environments with arbitrarily complicated
2865 When an internal host (193.233.7.83 in the example above)
2880 router (or 0.0.0.0) and masquerading is configured in the linux-2.2
2881 kernel. In this case the router will masquerade the packets as this address.
2885 NAT mechanism used in linux-2.4 is more flexible than
2910 destined for port 80 are marked with marker 0x1234 in input fwchain.
2911 In this case you may replace rule \#320 with:
2922 in the common case of a node attached to a single broadcast
2924 hosts and on routers, is described in the following
2927 The utilities used in the script may be found in the
2938 can be found in the \verb|dhcp.bootp.rarp| subdirectory of
3124 for dir in $sbase/*/forwarding; do
3183 case "$1" in
