Home | History | Annotate | Download | only in doc

Lines Matching refs:Error

157 \section{{\tt ip} --- error messages}
163 A syntax error on the command line: an unknown keyword, incorrectly formatted
164 IP address {\em et al\/}. In this case \verb|ip| prints an error message
165 and exits. As a rule, the error message will contain information
176 The kernel returned an error to some syscall. In this case \verb|ip|
177 prints the error message, as it is output with \verb|perror(3)|,
181 The kernel returned an error to some RTNETLINK request.
182 In this case \verb|ip| prints the error message, as it is output
194 It is difficult to list all the error messages (especially
218 RTNETLINK error: Invalid argument
541 These error names are pure Ethernetisms. Other devices
1161 The local senders get an \verb|EHOSTUNREACH| error.
1163 are discarded silently. The local senders get an \verb|EINVAL| error.
1166 prohibited\/} is generated. The local senders get an \verb|EACCES| error.
1176 is generated. The local senders get an \verb|ENETUNREACH| error.
1626 in an error. See attribute \verb|error| below (p.\pageref{IP-ROUTE-GET-error}).
1658 \item \verb|error| --- on \verb|reject| routes it is error code
1660 These error codes are translated into ICMP error codes, sent to remote
1663 \label{IP-ROUTE-GET-error}
2012 is unreachable'' error.
2014 ``Communication is administratively prohibited'' error.
2696 generating an error instead.
3256 echo "Error: cannot enable interface $dev." 1>&2
3269 echo "Error: some host already uses address $ipaddr on $dev." 1>&2
3280 echo "Error: failed to add $pfx on $dev." 1>&2