25 from the \verb|iproute2| package. It is not a tutorial or user's guide.
26 It is a {\em dictionary\/}, not explaining terms,
68 --- enforce the protocol family to use. If the option is not present,
70 line does not give enough information to guess the family, \verb|ip| falls back to the default
100  Do not use this option when reporting bugs or asking for advice.
130 do not allow all of these operations or have some additional commands.
151 but they are not recommended in scripts or when reporting bugs
169 The arguments did not pass verification for self-consistency.
188 if the \verb|ip| utility fails, it does not change anything
201 \item Netlink is not configured in the kernel. The message is:
206 \item RTNETLINK is not configured in the kernel. In this case
213 \item The \verb|CONFIG_IP_MULTIPLE_TABLES| option was not selected
253 This operation is {\em not allowed\/} if the device is in state \verb|UP|.
269 --- change the name of the device. This operation is not
294 Do not use it, if you do not understand what this operation really does.
306 obsolete and should not be changed administratively, though
386 does not queue anything and \verb|noop| means that the interface is in blackhole
398 \item \verb|LOOPBACK| --- the interface does not communicate with other
419 that software {\em must not\/} interpret the absence of this flag as the inability
423 Certainly, the use of high bandwidth multicast transfers is not recommended
424 on broadcast-only links because of high expense, but it is not strictly
428 traffic on the link even if it is not destined for us, not broadcasted
429 and not destined for a multicast group of which we are member. Usually
453 or not implemented (\verb|DEBUG|) or specific to some devices
454 (\verb|MASTER|, \verb|AUTOMEDIA| and \verb|PORTSEL|). We do not discuss
476 Multicast addresses are not shown by this command, see
553 different addresses attached to one device. These addresses are not
554 discriminated, so that the term {\em alias\/} is not quite appropriate
555 for them and we do not use it in this document.
603 Unlike \verb|ifconfig|, the \verb|ip| utility {\em does not\/} set any broadcast
663 It would be best not to repeat this experiment.
706 address configuration or only list permanent (not dynamic) addresses.
710 --- (IPv6 only) only list addresses which did not pass duplicate
752 --- the address is not used when selecting the default source address
780 --- the address is not used because duplicate address detection~\cite{RFC-ADDRCONF}
781 is still not complete or failed.
795 The difference is that it does not run when no arguments are given.
799 not forgive it, but will cruelly purge all the addresses.
892 This option to \verb|ip neigh| does not change the neighbour state if
893 it was valid and the address is not changed by this command.
929  The deleted neighbour entry will not disappear from the tables
962 --- only list neighbours which are not currently in use.
1049 The differences are that it does not run when no arguments are given,
1050 and that the default neighbour states to be flushed do not include
1125 of the routes is not essential. However, in this case,
1126 fiddling with default routes manually is not recommended. Use the Router Discovery
1128 instead. Actually, Linux-2.2 IPv6 does not give user level applications
1132 Certainly, the steps above are not performed exactly
1135 with minimal cost. However, not depending on a particular
1182 \item \verb|anycast| --- ({\em not implemented\/}) the destinations are
1187 It is not present in normal routing tables.
1199 this table automatically and the administrator usually need not modify it
1234 of the route and of the packet. If they are not equal, then the packet
1279 not used, the MTU may be updated by the kernel due to Path MTU Discovery.
1308     flag is not used.
1314     destinations when establishing TCP connections. If it is not given,
1324     If it is not given, Linux uses the value selected with \verb|sysctl|
1372 not given, \verb|ip| assumes protocol \verb|boot| (i.e.\
1387 The rest of the values are not reserved and the administrator is free
1388 to assign (or not to assign) protocol tags. At least, routing
1397 even if it does not match any interface prefix. One application of this
1432 Note the scope value. It is not necessary but it informs the kernel
1436 \item announce that the address 192.203.80.144 is not a real one, but
1490 and a prefix. \verb|root PREFIX| selects routes with prefixes not shorter
1492 \verb|match PREFIX| selects routes with prefixes not longer than
1494 \verb|10/8| and \verb|0/0|, but it does not select \verb|10.1/16| and
1616 additional attributes which normal routes do not possess.
1651 \item \verb|notify| --- ({\em not implemented}) change/deletion
1723 as the arguments of \verb|ip route show|, but routing tables are not
1726 The reason for this difference does not require any explanation, does it?
1828 Note that this operation is not equivalent to \verb|ip route show|.
1832 If the \verb|iif| argument is not given, the kernel creates a route
1881 and a ``multicast'' part. The normal part is used to deliver (or not to
1883 is not a member
1940 but not in practice, on the TOS field). The seminal review of classic
1943 In some circumstances we want to route packets differently depending not only
2023 Do not confuse routing tables with rules: rules point to routing tables,
2026 referring to a table, the table is not used, but it still exists
2035 These values do not override those contained in the routing tables. They
2036 are only used if the route did not select any attributes.
2101   Really, for historical reasons \verb|ip rule add| does not require a
2103   If the user does not supplied a priority, it is selected by the kernel.
2105   already exists, the kernel does not reject the request. It adds
2109   so do not rely on this feature. Use explicit priorities.
2120 succeeded. Realm \verb|TO| is only used if the route did not select
2128 In the last case the router does not translate the packets,
2136 do not become active immediately. It is assumed that after
2246 One additional feature not present in the example above
2296  It is not a bug, but rather a hole in the API and intra-kernel interfaces.
2298  with Linux-2.2 you {\em have to\/} be sure that the host is not
2299  a router and, especially, that it is not a transparent proxy or masquerading
2368 the number of packets that arrived on the wrong interface, if this number is not zero.
2440 	not be able to escape to another device when the route to endpoint changes.
2472  I think this option does not
2473 	work. At least, I did not test it, did not debug it and
2474 	do not even understand how it is supposed to work or for what
2475 	purpose Cisco planned to use it. Do not use it.
2527 \item \verb|DeadLoop| --- the total number of packets which were not
2529 \item \verb|NoRoute| --- the total number of packets which were not
2531 \item \verb|NoBufs| --- the total number of packets which were not
2553 If a file name is given, it does not listen on RTNETLINK,
2578 want to distinguish the packets not only by their destination, but
2592 does not allow such a simple approach.
2615 daemon is not aware of realms), missing realms may be completed
2624 If the destination realm was not inherited from the route and the rule has a destination realm,
2654 The realm \verb|russia| consists of routes with ASPATHs not leaving
2657 Note that locally originating packets are not accounted here,
2661 summarizing traffic not only by source or destination, but
2735  However, this hack {\em must not\/} be used on multihomed hosts
2750 \item IPv6 searches for the first valid, not deprecated address
2757 are not encoded in their addresses but are supplied
2769 in the search list, so that if an address with global scope (not 127.0.0.1!)
2783 the route to the requested destination does {\em not\/} go back via the same
2794 Logically, proxy ARP/NDISC is not a kernel task. It can easily be implemented
2815 If the name of the device is not given, the router will answer solicitations
2818 \verb|ip neigh|, the router {\em will not\/} answer a query if the route
2824 Particularly, the entry does not store any link layer address.
2837 \paragraph{What it is not:}
2838 It is necessary to emphasize that {\em it is not supposed\/}
2840 This is not missing functionality but a design principle.
2841 Route NAT is {\em stateless\/}. It does not hold any state
2845 using an address. For the same reason, it will not help to split
2854 The second feature: it does not touch packet payload,
2855 does not try to ``improve'' broken protocols by looking
2858 This also, is not missing any functionality.
2861 active FTP clients happy, your choice is not route NAT but masquerading,
2875 A great advantage of route NAT is that it may be used not
2877 structure. It does not firewall, it {\em forwards.}
2911 If it is just a random address the router will not map to it.
2925 when a packet does not leave this network. Let us return to the
2933 packets from 193.233.7.83 do not leave networks 193.233.7/24
2934 and 192.203.80/24. Also, if the \verb|inr.ruhep| table does not
3104 \# It is not so cheap though and we still hope that this route\\
3106 \# Do not make this step if the device is not ARPable,\\
3107 \# because dead nexthop detection does not work on them.
3128 namely, IP address management. It not only adds
3150 \# It returns 0, if the host is apparently not router.
3252 \# Otherwise, if prefix length was not given, guess it.
3343 \# Do not make this step on router or if the device is not ARPable.\\
3344 \# because dead nexthop detection does not work on them.

Indexes created Fri Mar 13 02:32:08 CET 2015