Red Hat Bugzilla – Bug 79581
Security Level screen does show iptables setting
Last modified: 2008-05-01 11:38:04 EDT
Description of problem:
Pretty much, on the System Settings->Security Level screen,
you want to hit "Customize", and allow eth devices, then if there
are specific ports to allow, enter those, then hit ok. If you
bring up the screen again, dont expect to see your changes--Hit Cancel
button or you will screw up your previous work. To actually verify your
port is open, do an iptables -L at the command line and check for your
port(s) to be open.
It is rather confusing that after initially changing settings on this
screen, bringing it up again does not show the settings as you left them.
If you added any ports these should show in the customized window below
telnet, etc. I understand that this is a front end to iptables, it would
be nice if it reflected iptables settings.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Go into Security level screen and click customize, add some ports at the
bottom. Click ok.
2.Do an iptables -L on command line. verify ports are open.
3. Go back into Security level screen again---previous settings are not
reflected---if you mistakenly click ok, you will change your iptables
settings. Click Cancel and verify on command line with iptables -L that your
ports are still open.
The first time I alter the Security level it changes the iptables settings
correctly when you click OK. Window closes. OPen the Security level screen
again and it looks as if the previous execution didn't work.
When I bring up the Security Level and change the settings and click OK the
iptables settings should change and window should close.
Any time after that if I bring up the Security level window, the window should
reflect the iptables settings by showing your previous selections.
I think you meant to say "Security Level does not show iptables setting?"
This also looks like a duplicate of bug 76500.
*** This bug has been marked as a duplicate of 76500 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.