QA:Testcase NM Ethernet

From FedoraProject

Jump to: navigation, search

Contents

Description

This test case cover Ethernet connection configuration via desktop GUIs. Both Gnome and KDE have similar GUI configuration tools with almost same options.

Setup

Have LAN connection available, preferably with IPv4/IPv6 dualstack support.

How to test

  1. Connect the ethernet cable. Then run ping fedoraproject.org and if you have IPv6 connection also: ping6 fedoraproject.org
  2. Disable and re-enable ethernet interface via Network Manager applet (Gnome or KDE) and run ping(s) again.
  3. Open "Options..." dialog in Gnome's "Network Settings" or "Edit..." dialog in KDE's "Network Management Settings". Configure IPv4/IPv6 address, gateway(s) and DNS(s) manually and run ping(s) again.

Expected Results

  1. If network has DHCP server running, you should get an IP Address, Default Route (gateway) and DNS addresses automatically. Check this via "Network Settings" in Gnome or "Network Management" applet in KDE and in terminal by running commands: ip address, ip route and ip -6 route. If network supports IPv6 autoconfiguration via DHCPv6 or SLAAC your interface should have two IPv6 addresses: First local-link starting with "fe80::" and second globally unique address provided by network. Ping(s) should be answered.
  2. When interface is disabled, check by running ip address if interface state is "DOWN" and doesn't have other IP addresses then local-link. Run ip route and ip -6 route and check if all routes from disabled network are removed. After enabling, interface should return to previous state. Ping(s) should be answered.
  3. Interface should be configured properly, check with ip address, ip route and ip -6 route. Ping(s) should be answered.

Optional

  1. Test various IPv4 and IPv6 configuration options, correct and even incorrect. Check how Network Manager handles this configurations and if it behaves as you expect.
  2. Test "802.1x Security", if you have an infrastructure or you are able to setup it.