From Fedora Project Wiki
< QA | Networking
(Created page with "== Operations == Requirements: * Support for both IPv4 and IPv6. * When applicable, IPv6 is preferred unless configured otherwise. * Explicit protocol selection. The most co...") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
Requirements: | Requirements: | ||
* Support | * Support both IPv4 and IPv6 protocols. | ||
* | * Support explicit protocol selection (e.g. via <code>-4</code> and <code>-6</code> and command-line options). | ||
* Prefer IPv6 by default. | |||
* Prefer IPv4 when configured so (e.g. via <code>/etc/gai.conf</code>). | |||
* Work well when IPv6 is disabled in the kernel (e.g. via <code>ipv6.disable=1</code> kernel option). | |||
Tools mimicking client behavior including ''ping'', ''tracepath'', ''nc'' and others should also comply with client behavior specified in [[../Client software|client sofware subpage]]. | |||
=== Example: ping === | |||
One of the most prominent network testing tools is ''ping''. It doesn't support IPv6 and instead a separate ''ping6'' tool is available. We are going to provide a version that fits all the requirements above. | |||
Latest revision as of 20:52, 27 October 2015
Operations
Requirements:
- Support both IPv4 and IPv6 protocols.
- Support explicit protocol selection (e.g. via
-4and-6and command-line options). - Prefer IPv6 by default.
- Prefer IPv4 when configured so (e.g. via
/etc/gai.conf). - Work well when IPv6 is disabled in the kernel (e.g. via
ipv6.disable=1kernel option).
Tools mimicking client behavior including ping, tracepath, nc and others should also comply with client behavior specified in client sofware subpage.
Example: ping
One of the most prominent network testing tools is ping. It doesn't support IPv6 and instead a separate ping6 tool is available. We are going to provide a version that fits all the requirements above.