Test Day:2012-03-19 firewalld

Fedora Test Days
firewalld
Date	<<2012-03-19>>
Time	all day
Website	QA/Fedora_17_test_days
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 installment of Fedora Test Day will focus on firewalld

Who's available

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

• Development / general help - Thomas Woerner (twoerner on FreeNode)
• Development / general help - Jiri Popelka (jpopelka on FreeNode)

Prerequisite for Test Day

• A fully updated Fedora 17 Alpha machine. See instructions below.
• Packages firewalld and firewall-applet installed.
• Disable and stop iptables, ip6tables and ebtables services:

 systemctl disable iptables.service
 systemctl disable ip6tables.service
 systemctl disable ebtables.service

• Make sure that the services are not running anymore

 systemctl status iptables.service
 systemctl status ip6tables.service
 systemctl status ebtables.service

Test Cases

• Test case 1: Firewalld usable and active
• Test case 2: Use firewall zones
• Test case 3: firewalld and NetworkManager
• Test case 4: firewall-applet

Optional Test Packages

These cases are optional, because the patches for the applicaitons are mostly not complete.

• control-center: Port Printers panel to FirewallD1 API: https://bugzilla.redhat.com/show_bug.cgi?id=802381
• libvirt
• system-config-printer

Test Results

If you have problems with any of the tests, report a bug to Bugzilla. For instance file a bug report against the component firewalld if you have problems testing firewlld. 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

Test Matrix

Package	Steps	Test Case	Tracker	Result	Bug	Comment