Lines Matching refs:we
377 Then we see the interface {\em mtu\/} (``maximal transfer unit''). This determines
417 \verb|BROADCAST| link is multicasting by definition, because we have
425 and not destined for a multicast group of which we are member. Usually
558 for them and we do not use it in this document.
1102 \item If we still have several routes, then the {\em first\/} of them
1112 For simplicity we will limit ourselves to the case where such a situation
1134 routing algorithm implemented in the kernel, we can summarize
1559 To count the size of the routing cache, we have to use the \verb|-o| option
1871 What happened? Router 193.233.7.254 understood that we have a much
1873 We may retry \verb|ip route get| to see what we have in the routing
1897 In some circumstances we want to route packets differently depending not only
2270 so we may only display them. This limitation will be removed
2501 \verb|OBJECT-LIST| is the list of object types that we want to monitor.
2530 tables may be huge. If we want to classify or to account for the packets
2531 per route, we will have to keep lots of information. Even worse, if we
2555 aggregates (we call them {\em realms\/}) is low, the task of full
2587 After this procedure is completed we know what realm the packet
2747 and in Linux-2.0, so we have to preserve it at least to the extent that
2968 \# If user gave loopback as device, we add the address as alias and exit.
3015 \# OK, the address is unique, we may add it on the interface.\\
3053 \# If a proxy ARP server is present on the interface, we will be\\
3055 \# It is not so cheap though and we still hope that this route\\
3292 \# If a proxy ARP server is present on the interface, we will be\\