Test Day:2015-08-20 NetworkManager

Fedora Test Days
Network Manager
Date	2015-08-20
Time	all day
Website
IRC	#fedora-test-day (webirc)
Mailing list	test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on NetworkManager. For Fedora 23, we update it to a new stable release, including a lots of fixes and a handful of new features. Let's make sure we didn't miss out regress anywhere and NetworkManager is easy and flawless to use.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - Lubomir Rintel (lrintel)

(<<FIXME>>: remove the template below when filed in:)

• Development - Developer1 (irc_nick1), Developer2 (irc_nick2)
• Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4), Tester3 (irc_nick5)

Prerequisite for Test Day

• An updated Fedora 23 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image

Testing in various setups is welcome, may require additional setups, e.g.:

• IPv6-enabled and legacy-free networks (no IPv4)
• Wireless access points with various security mechanisms (WPA, WEP, ...)
• Multiple links to the same network, wireless & wired
• Server setups, bonding, teaming, bridging, vlans (possibly stacked)
• Other tools that namange networking installed for testing interoperability: libvirt, Docker, VMWare, VirtualBox, systemd-networkd, ...
• A Mobile broadband connectivity dongle
• Bluetooth DUN & PAN enabled dongle or a phone
• VPN servers, concentrators
• Different desktop environemnts installed, to test integration: GNOME, KDE, Xfce, ...

How to test?

A default Fedora Workstation setup will do.

If you discover a bug, you might be asked to raise your logging level in NetworkManager.conf or with nmcli so that we could get a trace of what went wrong.

Update your machine

If you're running Fedora 23, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image

Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

Test Cases

You're encouraged to test whichever setups you're generally using and let us know how well does the new NetworkManager works for you.

Here's some existing test plans that may help you with deciding what to test:

Wireless

• Wireless
• WiFi
• WEP
• WPA
• GNOME Hotspot
• KDE Hotspot

VPN

• OpenVPN
• vpnc

Mobile connectivity

• Mobile Broadband
• Bluetooth PAN
• Cellular connection provider database

Advanced

• IPv6
• Ethernet
• Bonding
• Command line functionality
• DNS-over-SSL
• DNSSEC-trigger
• Connection assumption

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component NetworkManager, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=23&component=network-manager-applet network-manager-applet for bugs in the applet or connection editor itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

User	Wireless	VPN	Mobile	Advanced	Other	References
Lubomir Rintel	none	pass	warn	fail	warn