Bug 755241 - Saving and restoring iptables rules documentation needs update for systemd
Summary: Saving and restoring iptables rules documentation needs update for systemd
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: security-guide
Version: devel
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eric Christensen
QA Contact: Fedora Docs QA
URL:
Whiteboard:
: 757335 757761 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-19 23:25 UTC by D J Capelis
Modified: 2013-06-03 17:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-03 17:29:46 UTC


Attachments (Terms of Use)

Description D J Capelis 2011-11-19 23:25:38 UTC
Might want to use #707687 as a tracking bug for these types of issues.

This is out of date and needs to be updated for the post-systemd world:
https://docs.fedoraproject.org/en-US/Fedora/16/html/Security_Guide/sect-Security_Guide-IPTables-Saving_IPTables_Rules.html

Didn't see this filed anywhere else, so figured I'd submit it.  Systemd doesn't actually even allow you to use "save" anymore, so it's somewhat unclear how people are supposed to do this, it would be nice if the documentation provided guidance.

Comment 1 eric 2011-11-28 16:16:03 UTC
*** Bug 757761 has been marked as a duplicate of this bug. ***

Comment 2 Karsten Wade 2011-12-14 03:45:58 UTC
Removing myself for these bug components as I'm either no longer involved in that aspect of the project, or no longer care to watch this particular bug. Sorry if you are caught in a maelstrom of bug changes as a result!

Comment 3 Paul 2012-01-16 03:32:52 UTC
I bumped into this while bring up a system under F16 (i686 Xfce). The best I could find online was to do "iptables-save > /etc/sysconfig/iptables" which works.

Is the plan to allow systemd to understand what "service iptables save" used to do or to change the documentation to suggest the above workaround as the new way to do it ... or something else?

Thanks,
Paul

Comment 4 eric 2012-02-28 22:20:05 UTC
*** Bug 757335 has been marked as a duplicate of this bug. ***

Comment 5 Eric Christensen 2013-06-03 17:29:46 UTC
This is being fixed by an update to the firewall chapter.


Note You need to log in before you can comment on or make changes to this bug.