Bug 317751 - Need to restart iptables after changing system-config-firewall settings
Need to restart iptables after changing system-config-firewall settings
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: system-config-firewall (Show other bugs)
6
i386 Linux
low Severity high
: ---
: ---
Assigned To: Thomas Woerner
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-04 00:08 EDT by Marcel Lecker
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-06 11:26:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marcel Lecker 2007-10-04 00:08:38 EDT
Description of problem:
-Need to restart iptables after changing settings in System-config-firewall
before new settings take effect 

Version-Release number of selected component (if applicable):
-unknown

How reproducible:
-unkown

Steps to Reproduce:
1. Open system-config-firewall, open a port, save and close.
2. examine iptables, do a port-scan etc. note the absence of changes
3. restart iptables, note changes having taken effect.
  
Actual results:
- system-config-firewall changes do not take immediate effect

Expected results:
- once settings are saved changes should take effect.

Additional info:
- none
Comment 1 Thomas Woerner 2007-10-04 04:46:59 EDT
system-config-firewall is part of FC-8 and later, so ar you sure, that you are
not using system-config-securitylevel?

Please supply the Version-Release of system-config-securitylevel.
What have you changed in your settings?
Comment 2 Thomas Woerner 2007-11-06 11:26:20 EST
This bug entry was in needinfo for some time. Closing due to user inactivity as
"NOT A BUG".

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