Lines Matching refs:may
27 but translating them into other terms, which may also be unknown to the reader.
39 bugs and design drawbacks. They may be skipped at the first reading.
49 begin with the character \verb|'-'| and may be used in either long or abbreviated
122 Again, the names of all objects may be written in full or
143 which may be omitted. F.e.\ parameter \verb|dev| is the default
149 Almost all keywords may be abbreviated with several first (or even single)
159 \verb|ip| may fail for one of the following reasons:
191 which may change only some of the device parameters given
207 one of the following messages may be printed, depending on the command:
364 unique at every given moment. However, the interface may disappear from the
366 one with the same name may be created later. Besides that,
367 the administrator may change the name of any device with
371 The interface name may have another name or \verb|NONE| appended
391 packets for transmission and it may inject into the kernel packets received
469 types may have their natural address format, f.e.\ addresses
475 however this field may contain useful information, f.e.\
519 on Ethernet-like media. This number may have a different sense on other
545 may have non zero values in these fields but they may be
583 separated by colons for IPv6. The \verb|ADDRESS| may be followed by
590 Again, the \verb|ADDRESS| may be followed by a slash and a decimal number,
613 --- Each address may be tagged with a label string.
675 may be found in sec.\ref{IP-ADDR-FLUSH}, p.\pageref{IP-ADDR-FLUSH}.
935 a \verb|noarp| entry created by the kernel may result in unpredictable behaviour.
936 Particularly, the kernel may try to resolve this address even
966 This option may occur more than once. If this option is absent, \verb|ip|
1010 may remove the entry from the neighbour table.
1233 may still match a route with a zero TOS. \verb|TOS| is either an 8 bit hexadecimal
1244 \verb|TABLEID| may be a number or a string from the file
1270 \verb|REALMID| may be a number or a string from the file
1277 not used, the MTU may be updated by the kernel due to Path MTU Discovery.
1316 If the path to these destination is asymmetric, this guess may be wrong.
1341 \verb|SCOPE_VAL| may be a number or a string from the file
1351 \verb|RTPROTO| may be a number or a string from the file
1379 option may be found in~\cite{IP-TUNNELS}.
1497 \verb|table| \verb|main|. \verb|TABLEID| may either be the ID of a real table
1570 However, some records may consist
1778 If policy routing is used, it may be a different route.
1873 We may retry \verb|ip route get| to see what we have in the routing
1913 by executing some set of rules. The rules may have lots of keys of different
1935 the action is performed. The action predicate may return with success.
1966 routes. This rule may be deleted and/or overridden with other
1973 This rule may also be deleted.
1978 several rules may refer to one routing table and some routing tables
1979 may have no rules pointing to them. If the administrator deletes all the rules
1993 \paragraph{Rule types:} The RPDB may contain rules of the following
2039 may create separate routing tables for forwarded and local packets and,
2080 The \verb|ADDRESS| may be either the start of the block of NAT addresses
2247 The effects may be strange. Namely, the addresses become additional
2270 so we may only display them. This limitation will be removed
2502 It may contain \verb|link|, \verb|address| and \verb|route|.
2530 tables may be huge. If we want to classify or to account for the packets
2558 So each route may be assigned to a realm. It is assumed that
2569 daemon is not aware of realms), missing realms may be completed
2669 the backward path may appear different to the forward one which
2671 are administratively scoped, the reply may be lost entirely.
2677 The application may select a source address explicitly with \verb|bind(2)|
2729 Routers may answer ARP/NDISC solicitations on behalf of other hosts.
2730 In Linux-2.2 proxy ARP on an interface may be enabled
2815 By the way, you may also want to look at
2823 inside your network. No other hosts may use these addresses,
2824 however other routers may also be configured to translate them.
2826 A great advantage of route NAT is that it may be used not
2843 blocks of addresses, you may use a command like:
2892 and leave the rest intact, you may use \verb|ipchains|
2896 In this case you may replace rule \#320 with:
2908 network. A more advanced script, which may be used both on multihomed
2912 The utilities used in the script may be found in the
3015 \# OK, the address is unique, we may add it on the interface.\\
3094 \# ---Device name. It may have alias suffix, separated by colon.\\
3259 \# OK, the address is unique. We may add it to the interface.\\