|Line 126:||Line 126:|
Revision as of 11:05, 12 December 2012
|Fedora Test Days|
|Mail • Subscribe • Archives|
What to test?
Today's installment of Fedora Test Day will focus on FirewallD
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Thomas Woerner (twoerner on FreeNode)
- Development - Jiri Popelka (jpopelka on FreeNode)
- Development (Network Manager) - Pavel Šimerda (pavlix on FreeNode)
- Quality Assurance - Petr Sklenar (psklenar on FreeNode)
- Quality Assurance - Martin Holec (Martix on FreeNode)
Prerequisite for Test Day
Make sure you have all current updates (and temporal fixes) installed by:
# yum update
Clear your audit log (especially important in case you aren't running from the live medium):
# echo -n > /var/log/audit/audit.log
2. Packages firewalld, firewall-config (Test case 5) and firewall-applet (Test case 6) installed.
# yum install firewalld firewall-config firewall-applet
3. 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
4. Make sure that the services are not running anymore
systemctl status iptables.service systemctl status ip6tables.service systemctl status ebtables.service
- Test case 1: Firewalld usable and active
- Test case 2: FirewallD and NetworkManager
- Test case 3: Persistent changes of firewall zones
- Test case 4: Runtime changes of firewall zones
- Test case 5: firewall-config
- Test case 6: firewall-applet
- Test case 7: system-config-printer
- Test case 8: selinux-AVCs
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.