QA:Testcase Basic networking

QA:Testcase Basic networking

Description

This test case verifies that a Fedora system allows the network to access the Internet over IPv4, and over IPv6 if available. It focuses on typical user workflows, such as connecting to Wi-Fi or wired network, reaching the router, and using common Internet services (web, DNS, optional SSH).

No virtual machines or special server setup are required. Run this test on your usual Fedora installation and network.

Setup

1. Boot the installed Fedora system you want to test.
2. Connect it to your usual network:
   • Wi-Fi: Use Settings → Wi-Fi (GNOME) or System Settings → Wi-Fi and Internet (KDE) to connect to your regular access point.
   • Wired: Plug in the network cable; your computer should connect automatically.
3. Keep the default automatic configuration (DHCP for IPv4, SLAAC/DHCPv6 for IPv6). Only change the settings, if you networking environment is not configured for automatic IP assignement.

How to test

Verify the network configuration

1. Open a terminal.
2. Check that at least one network interface is up and has an IPv4 address:

   ip -4 addr show

   This command will show all active connections. Look for an interface with state UP and an inet address (for example 192.168.1.23/24). That indicates that your connection is active and your IPv4 IP address is 192.168.1.23. The IP address may vary depending on your network environment.

3. If your provider supports IPv6, also check for IPv6 addresses:

   ip -6 addr show

   Look for an interface with state UP and a global inet6 address (do not rely only on fe80:: link-local addresses).

4. Show the default IPv4 route:

   ip -4 route | grep default

   You should see a line like

   default via 192.168.1.1 ...

   The address after via is your router.

5. Optionally, show the default IPv6 route:

   ip -6 route | grep default

   If your ISP/router provides IPv6, you should see a default via line. If you do not see it, continue with IPv4 testing only.

Test basic connectivity

1. Ping your router over IPv4 (replace the address with the via address from the previous step, for example 192.168.1.1):

   ping -c10 192.168.1.1

   All packets should be received and there should not be any package loss.

2. Test IPv4 connectivity to the Internet using a well-known public IP (for example Cloudflare DNS):

   ping -c10 1.1.1.1

3. Test IPv4 connectivity by hostname (this also checks DNS resolution):

   ping -c10 fedoraproject.org

4. (Optional, IPv6) Test IPv6 connectivity to a public IPv6 address (Cloudflare IPv6 DNS):

   ping -6 -c3 2606:4700:4700::1111

5. (Optional, IPv6) Test IPv6 connectivity by hostname:

   ping -6 -c3 fedoraproject.org

Test HTTP / HTTPS access

You can use either a web browser or the curl command.

1. Open a web browser and load these pages:
   • https://fedoraproject.org
   • https://www.kernel.org (or another well-known site)

   Both pages should load without network errors.

2. From a terminal, fetch a page over IPv4:

   curl -4 https://fedoraproject.org/

   You should see HTML output and no connection errors.

3. Optionally, fetch a page over IPv6 (if your ISP provides IPv6):

   curl -6 https://fedoraproject.org/

(Optional) Test SSH access

This step is only for testers who already have access to an SSH server (for example a VPS, home NAS, or another Linux machine).

1. Try to open an SSH session over IPv4:

   ssh username@your-server.example.org

   or, if you use an IPv4 address directly:

   ssh username@203.0.113.10

2. If your server has a public IPv6 address, also test:

   ssh username@[your-ipv6-address]

   Reaching a password or key prompt is considered a success; you can cancel with Ctrl+C after confirming the connection is established.

Expected Results

• At least one network interface is up and has a valid IPv4 address assigned from your home/office network.
• If your ISP provides IPv6, the system has a valid global IPv6 address and a default IPv6 route.
• Default routes for IPv4 (and IPv6 if applicable) are present and point to your router.
• The system can reach the local router with ICMP echo (ping) over IPv4 (and IPv6, if tested) without unexpected packet loss.
• The system can reach the public Internet by IP address and by hostname, confirming both connectivity and DNS resolution.
• HTTP/HTTPS access to well-known public web sites works in the browser and with curl (no client-side network errors).
• If an SSH server is available, SSH connections can be established over IPv4 (and IPv6, if tested).
• All operations complete without crashes, hangs, or obvious misbehavior in the desktop networking tools or NetworkManager.