From Fedora Project Wiki
Fedora Test Days
Echo-testing-48px.png
firewalld

Date 2012-03-19
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 ...

Prerequisite for Test Day

  • A fully updated Fedora 17 Alpha machine. You should have firewalld version 0.2.4-1.fc17 installed.
  • Packages firewalld and firewall-applet installed.
  • Disable and stop iptables, ip6tables and ebtables services:
 systemctl disable iptables.service
 systemctl stop iptables.service
 systemctl disable ip6tables.service
 systemctl stop ip6tables.service
 systemctl disable ebtables.service
 systemctl stop 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

Optional Tests and Test Packages

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

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

User Firewalld usable and active Use firewall zones firewalld and NetworkManager firewall-applet Optional Tests References
Sample User
none
Pass pass
Warning warn
[1]
Fail fail
[2]
Pass pass
system-config-printer, libvirt
  1. Test 3.1 failed RHBZ #54321 (firewall-cmd --list=all --zone=public failed with an error)
  2. RHBZ #12345
pavlix
Pass pass
Pass pass
Fail fail
[1]
none
none
  1. RHBZ #804587
nphilipp
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
system-config-printer,
Pass pass
initscripts
sagitter
Pass pass
Pass pass
Fail fail
[1] [2]
Fail fail
[3]
none
  1. RHBZ #804587
  2. command not found 'firewalld-cmd --set-default-zone=...'
  3. firewalld-applet doesn't work. Error: $ /usr/lib64/python2.7/site-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed
    applet gone after closing terminal to have more information why it is on failed

Reference