From Fedora Project Wiki

< QA
No edit summary
 
(53 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Testing IPv6 support and dualstack networking can be very tricky. The purpose of this document is to provide a live resource on testing situations arising from existance and usage of two network layer protocols.
Main purpose of the Networking QA project is to check and improve IPv6 support in Fedora and concurrent usage of IPv4 and IPv6 protocols. Maintaining and improving existing IPv4 support is one of the secondary goals.


Base system components related to IPv6 and dual-stack operation:
== Contacts ==


* kernel
Coordinators:
* glibc


== Configuration ==
* [[User:pavlix|Pavel Šimerda]]
* [[User:thozza|Tomáš Hozza]]


== Name resolution ==
Contributors:


Name resolution features are provided by the GNU C Library (glibc) which is not yet ready for proper IPv6 and dual-stack operation as you can see when performing your tests. The C library comes with its own testing tool <code>getent</code> that has a special database called <code>ahosts</code> that runs <code>getaddrinfo()</code>, the library function that translates names to objects with addressing information. For your testing it is best used together with tools like <code>strace</code>, <code>ltrace</code> or even <code>gdb</code> so that you know exactly what is happening behind the scenes.
* [[User:nmav|Nikos Mavrogiannopoulos]] – iputils


As the <code>getent</code> tool is very primitive, we created a tool called <code>getaddrinfo</code> just as the library function that handles a larger subset of the function's API.
Potential contributors:


=== Name resolution input ===
* [[User:Tobygoodwin|Toby Goodwin]]


When application requests addressing information for a hostname with an optional service name, the library returns a list of addressing information objects. The order of objects in the list is significant and depends on operating system configuration and connectivity.
== Objectives ==


==== From the application ====
Note: We are trying to define objectives of the project. Unfortunately we cannot add everything someone considers good or important but we rather have focus on things that we can actually do. Contact us if you're willing to help with some topic that you're interested in or that you consider neglected.


* nodename
We would like to test, document and improve the following:
* servname
 
* protocol
* Automatic network configuration of a Fedora node
* socktype
* Proper dual-stack operation of client and server software in various environments
* flags
* Check Fedora infrastructure and installation for IPv6 only operation
** <code>AI_CANONNAME</code>
 
** ...
 
== Overview ==
 
Packages to test:
 
* [[/Packages]]
 
How to prepare test environment:
 
* [[/Test environment]]


==== From local configuration and connectivity checks ====
How to test different types of packages:


* Files in <code>/etc/</code> including nsswitch, hosts, services and more
* [[/Configuration]]
* To what extend is IPv4 and IPv6 available
* [[/Name resolution]]
* [[/Testing tools]]
* [[/Client software]]
* [[/Server software]]


==== From the outside world ====
Known issues:


* DNS information
* [https://bugzilla.redhat.com/showdependencytree.cgi?id=883152 Bugzilla tickets]
* Multicast DNS information
* LDAP information


=== Name resolution processing ===
== New packages ==


==== What is requested ====
There are new packages being added for networking and especially IPv6 testing and operations.


Not all information is requested at all times. Some information like canonical name must be explicitly requested by the application via <code>AI_CANONNAME</code> flag. It may be desirable to suppress other requests by local configuration or connectivity checks, a notable example being suppression of DNS AAAA queries on hosts without global connectivity.
* [https://bugzilla.redhat.com/show_bug.cgi?id=1265628 dhcpcd] – provides a basic network configuration daemon for testing and comparison
* [https://bugzilla.redhat.com/show_bug.cgi?id=1090499 netresolve] – provides a library, testing tools and example implementations for some network software operations


==== What is passed to the application ====
== Packages ==


Not all information that is learnt via requests is presented to the application. It is typically filtered according to input from the application. It is sometimes also filtered according to connectivity checks but that has caused more problems than improvements.
Note: This section is informative only. It only includes assessment of packages based on experience and is ''not'' a result of extensive testing.


==== How it is sorted ====
=== Packages working more or less well in IPv6 and dual-stack environments ===


There are rules for sorting addressing information returned by <code>getaddrinfo()</code>. One of the basic features is to return global IPv6 destinations before global IPv4 destinations. But when the library detects that IPv6 connectivity is not available, the reverse applies.
Following packages play more or less well with IPv6. You can still expect minor issues including delays when configuration of one of the protocols doesn't work as expected. Those packages are still to be tested.


=== Example tests ===
Network configuration:


==== Dual-stack host, destination with global IPv4 and IPv6 ====
* dhcp – Dynamic host configuration protocol software
* iproute – Advanced IP routing and network device configuration tools
* NetworkManager – Network connection manager and user applications
* dnssec-trigger – NetworkManager plugin to update/reconfigure DNSSEC resolving


On a host with IPv4 and IPv6 connectivity we request addressing information of another host that is announced as dual-stack in DNS.
Services:


<pre>
* bind – The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
$ getent ahosts www.nix.cz
* dnsmasq – A lightweight DHCP/caching DNS server
2a02:38::1001  STREAM info.nix.cz
* httpd – Apache HTTP Server
2a02:38::1001  DGRAM 
* openssh – An open source implementation of SSH protocol versions 1 and 2
2a02:38::1001  RAW   
* postfix – Postfix Mail Transport Agent
195.47.235.3    STREAM
195.47.235.3    DGRAM 
195.47.235.3    RAW
</pre>


You can see that <code>getaddrinfo()</code> returned ''six'' items for ''two'' unique IP addresses with the IPv6 address sorted first. If you only expected only ''two'' items, one for each IP address, see [https://sourceware.org/bugzilla/show_bug.cgi?id=14990 upstream bug 14990].
Development:


==== IPv4-only host, destination with global IPv4 and IPv6 ====
* git


We do the same on a host without IPv6 connectivity.
Other:


<pre>
* curl – A utility for getting files from remote servers (FTP, HTTP, and others)
$ getent ahosts www.nix.cz
* cyrus-imapd – A high-performance mail server with IMAP, POP3, NNTP and SIEVE support
195.47.235.3    STREAM info.nix.cz
* c-ares – A library that performs asynchronous DNS operations
195.47.235.3    DGRAM 
* firefox – Mozilla Firefox Web browser
195.47.235.3    RAW   
* libssh2 – A library implementing the SSH2 protocol
2a02:38::1001  STREAM
* iptables – Tools for managing Linux kernel packet filtering capabilities
2a02:38::1001  DGRAM 
2a02:38::1001  RAW   
</pre>


You can see that the result is the same as before except that IPv4 is sorted first.
=== Packages with severe issues in IPv6 and dual-stack environments ===


== Testing client applications ==
Core system:


=== Client application checklist ===
* avahi – Local network service discovery
** IPv6 turned off by default
** nss-mdns doesn't do IPv6LL due to glibc limitations
* glibc – The GNU libc libraries
** limited and buggy getaddrinfo()
** [https://sourceware.org/bugzilla/buglist.cgi?quicksearch=getaddrinfo upstream getaddrinfo issues]


A client application should:
Core tools:


* avoid using obsolete functions:
* iputils – Network monitoring tools including ping
** <code>gethostbyname()</code>, <code>gethostbyname2()</code>
** ping (unreleased upstream now supports dual-stack operation)
** <code>gethostbyaddr()</code>
** tracepath
** ...
** ...
* use system wide name resolution configuration
* quota – File system quota management
** avoid implementing name resolution code in the application
** [https://bugzilla.redhat.com/show_bug.cgi?id=704219 rpc.rquotad and other program should be ported from glibc's Sun RPC to tirpc's RPC]
** avoid calling DNS libraries directly (there are other name resolution sources than DNS)
*** [[User:Pavlix]]: Why and how is it related to IPv6?
**  
* [https://bugzilla.redhat.com/show_bug.cgi?id=1221496 fping: lack of IPv6 support]
* reduce timeouts when a fallback is available
* [https://bugzilla.redhat.com/show_bug.cgi?id=1220825 nslookup: bad default behavior]
** reduce excessive DNS timeouts, possibly using a decent system wide name resolution library
 
** reduce excessive TCP timeouts, possibly using a decent socket library
Development:
* attempt all provided addresses until one succeeds or all fail
 
** possibly using a decent socket library
* subversion - A Modern Concurrent Version Control System
** [https://bugzilla.redhat.com/show_bug.cgi?id=1130328 no fallback to IPv4 when IPv6 default route fails]
 
=== IPv4 only packages ===
 
Following packages do not need any IPv6 testing as they contain IPv4 specific tools.
 
* arptables
* arpwatch
 
=== Unqualified packages ===
 
Following packages weren't categorized yet but are considered important enough to be checked for IPv6 support. Please extend the list with other high visibility packages. You can add more important packages here.
 
Core system:
 
* abrt – Automatic bug detection and reporting tool
* anaconda – Graphical system installer
* apr – Apache Portable Runtime library
* busybox – Statically linked binary providing simplified versions of system commands
** It would be useful to check network related commands
* docker – Automates deployment of containerized applications
** IPv6 in /etc/resolv.conf
** IPv6 on bridged networks
* dracut – Initramfs generator using udev
* firewalld – A firewall daemon with D-BUS interface providing a dynamic firewall
* glib2/glib-networking – Networking support for GLib
* grub2 – Bootloader with support for Linux, Multiboot and more
* systemd – A System and Service Manager
* yum – RPM package installer/updater/manager
 
Services:
 
* bird – routing daemon
* cups – Common Unix Printing System
* dovecot – Secure imap and pop3 server
* openswan/libreswan/strongswan – IPSEC implementation with IKEv1 and IKEv2 keying protocols
 
* quagga – Routing daemon
* sendmail – A widely used Mail Transport Agent (MTA)
 
Development:


=== Known problematic packages ===
* bzr – Friendly distributed version control system
* cvs – Concurrent Versions System
* gdb – A GNU source-level debugger for C, C++, Fortran and other languages
* mercurial – Mercurial – a distributed SCM


* [https://bugzilla.redhat.com/show_bug.cgi?id=1130328 subversion: attempts the first address and gives up]
Other:


== Testing server applications ==
* apr-util – Apache Portable Runtime Utility library
** various networking tools including ping
* gvfs – Backends for the gio framework in GLib
* ipxe – A network boot loader
* iptstate – A top-like display of IP Tables state table entries
* ldns – Low–level DNS(SEC) library with API
* lftp – A sophisticated file transfer program
* libevent
* libvirt – Library providing a simple virtualization API
* net-tools – Basic networking tools
* nmap – Network exploration tool and security scanner
* nss-myhostname – glibc plugin for local system host name resolution
* nss – Network Security Services
* postgresql – PostgreSQL client programs
* rsync – A program for synchronizing files over a network
* squid – The Squid proxy caching server
* sssd – System Security Services Daemon
* syslinux – Simple kernel loader which boots from a FAT filesystem
* tcpdump – A network traffic monitoring tool
* telnet – The client program for the Telnet remote login protocol
* traceroute – Traces the route taken by packets over an IPv4/IPv6 network
* vinagre – VNC client for GNOME
* vino – A remote desktop system for GNOME
* virt-manager – Virtual Machine Manager
* virt-viewer – Virtual Machine Viewer
* wireshark – Network traffic analyzer

Latest revision as of 10:50, 14 December 2015

Main purpose of the Networking QA project is to check and improve IPv6 support in Fedora and concurrent usage of IPv4 and IPv6 protocols. Maintaining and improving existing IPv4 support is one of the secondary goals.

Contacts

Coordinators:

Contributors:

Potential contributors:

Objectives

Note: We are trying to define objectives of the project. Unfortunately we cannot add everything someone considers good or important but we rather have focus on things that we can actually do. Contact us if you're willing to help with some topic that you're interested in or that you consider neglected.

We would like to test, document and improve the following:

  • Automatic network configuration of a Fedora node
  • Proper dual-stack operation of client and server software in various environments
  • Check Fedora infrastructure and installation for IPv6 only operation


Overview

Packages to test:

How to prepare test environment:

How to test different types of packages:

Known issues:

New packages

There are new packages being added for networking and especially IPv6 testing and operations.

  • dhcpcd – provides a basic network configuration daemon for testing and comparison
  • netresolve – provides a library, testing tools and example implementations for some network software operations

Packages

Note: This section is informative only. It only includes assessment of packages based on experience and is not a result of extensive testing.

Packages working more or less well in IPv6 and dual-stack environments

Following packages play more or less well with IPv6. You can still expect minor issues including delays when configuration of one of the protocols doesn't work as expected. Those packages are still to be tested.

Network configuration:

  • dhcp – Dynamic host configuration protocol software
  • iproute – Advanced IP routing and network device configuration tools
  • NetworkManager – Network connection manager and user applications
  • dnssec-trigger – NetworkManager plugin to update/reconfigure DNSSEC resolving

Services:

  • bind – The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
  • dnsmasq – A lightweight DHCP/caching DNS server
  • httpd – Apache HTTP Server
  • openssh – An open source implementation of SSH protocol versions 1 and 2
  • postfix – Postfix Mail Transport Agent

Development:

  • git

Other:

  • curl – A utility for getting files from remote servers (FTP, HTTP, and others)
  • cyrus-imapd – A high-performance mail server with IMAP, POP3, NNTP and SIEVE support
  • c-ares – A library that performs asynchronous DNS operations
  • firefox – Mozilla Firefox Web browser
  • libssh2 – A library implementing the SSH2 protocol
  • iptables – Tools for managing Linux kernel packet filtering capabilities

Packages with severe issues in IPv6 and dual-stack environments

Core system:

  • avahi – Local network service discovery
    • IPv6 turned off by default
    • nss-mdns doesn't do IPv6LL due to glibc limitations
  • glibc – The GNU libc libraries

Core tools:

Development:

IPv4 only packages

Following packages do not need any IPv6 testing as they contain IPv4 specific tools.

  • arptables
  • arpwatch

Unqualified packages

Following packages weren't categorized yet but are considered important enough to be checked for IPv6 support. Please extend the list with other high visibility packages. You can add more important packages here.

Core system:

  • abrt – Automatic bug detection and reporting tool
  • anaconda – Graphical system installer
  • apr – Apache Portable Runtime library
  • busybox – Statically linked binary providing simplified versions of system commands
    • It would be useful to check network related commands
  • docker – Automates deployment of containerized applications
    • IPv6 in /etc/resolv.conf
    • IPv6 on bridged networks
  • dracut – Initramfs generator using udev
  • firewalld – A firewall daemon with D-BUS interface providing a dynamic firewall
  • glib2/glib-networking – Networking support for GLib
  • grub2 – Bootloader with support for Linux, Multiboot and more
  • systemd – A System and Service Manager
  • yum – RPM package installer/updater/manager

Services:

  • bird – routing daemon
  • cups – Common Unix Printing System
  • dovecot – Secure imap and pop3 server
  • openswan/libreswan/strongswan – IPSEC implementation with IKEv1 and IKEv2 keying protocols
  • quagga – Routing daemon
  • sendmail – A widely used Mail Transport Agent (MTA)

Development:

  • bzr – Friendly distributed version control system
  • cvs – Concurrent Versions System
  • gdb – A GNU source-level debugger for C, C++, Fortran and other languages
  • mercurial – Mercurial – a distributed SCM

Other:

  • apr-util – Apache Portable Runtime Utility library
    • various networking tools including ping
  • gvfs – Backends for the gio framework in GLib
  • ipxe – A network boot loader
  • iptstate – A top-like display of IP Tables state table entries
  • ldns – Low–level DNS(SEC) library with API
  • lftp – A sophisticated file transfer program
  • libevent
  • libvirt – Library providing a simple virtualization API
  • net-tools – Basic networking tools
  • nmap – Network exploration tool and security scanner
  • nss-myhostname – glibc plugin for local system host name resolution
  • nss – Network Security Services
  • postgresql – PostgreSQL client programs
  • rsync – A program for synchronizing files over a network
  • squid – The Squid proxy caching server
  • sssd – System Security Services Daemon
  • syslinux – Simple kernel loader which boots from a FAT filesystem
  • tcpdump – A network traffic monitoring tool
  • telnet – The client program for the Telnet remote login protocol
  • traceroute – Traces the route taken by packets over an IPv4/IPv6 network
  • vinagre – VNC client for GNOME
  • vino – A remote desktop system for GNOME
  • virt-manager – Virtual Machine Manager
  • virt-viewer – Virtual Machine Viewer
  • wireshark – Network traffic analyzer
Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Networking&oldid=430187"