I simply enabled the basic firewall. What exactly I did:-
http://sites.google.com/site/indiadoor/firewall-enabled
(This site was created by my friend, he simple wrote what I did by searching from here and there and without knowledge, so that i could recall what i did, if at any stage in the future required.)
and then when I click to see the Firewall (from System -> Administration -> Firewall and then providing the root credentials), the only thing which appears is a box and above which is written Firewall but in fact, nothing is getting displayed inside that but only blank.
What might be the error, because Firewall is working, that is enabled (which I checked in System -> Administration -> Services -> iptables), which I saw from google (that is I googled for how to check firewall is working). But is not getting displayed in GUI...!
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
I simply enabled the basic firewall. What exactly I did:-
http://sites.google.com/site/indiadoor/firewall-enabled ... and then when I click to see the Firewall (from System -> Administration -> Firewall and then providing the root credentials), the only thing which appears is a box and above which is written Firewall but in fact, nothing is getting displayed inside that but only blank.
Hi, Read the instructions of the web site you cited above and check if the firewall has any rules stored: [root@localhost ~]# cat /etc/sysconfig/iptables and [root@localhost ~]# cat /etc/sysconfig/ip6tables
Another option is to reinstall firewall and start from scratch (but then pay attention what you do next configuring it because the app may indeed have some bug to report). JB
On Fri, Jul 23, 2010 at 12:25 PM, JB jb.123abc@yahoo.com wrote:
Read the instructions of the web site you cited above and check if the firewall has any rules stored: [root@localhost ~]# cat /etc/sysconfig/iptables and [root@localhost ~]# cat /etc/sysconfig/ip6tables
Another option is to reinstall firewall and start from scratch (but then pay attention what you do next configuring it because the app may indeed have some bug to report). JB
I check that way,
Regards, Parshwa Murdia
On Fri, Jul 23, 2010 at 12:25 PM, JB jb.123abc@yahoo.com wrote:
Read the instructions of the web site you cited above and check if the firewall has any rules stored: [root@localhost ~]# cat /etc/sysconfig/iptables and [root@localhost ~]# cat /etc/sysconfig/ip6tables
Another option is to reinstall firewall and start from scratch (but then pay attention what you do next configuring it because the app may indeed have some bug to report). JB
Further see the error:
http://sites.google.com/site/indiadoor/firewall_error
It is showing blank. And there are no rules stored except those which come by default while enabling via gui.
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
On Fri, Jul 23, 2010 at 12:25 PM, JB <jb.123abc <at> yahoo.com> wrote: ...
Another option is to reinstall firewall and start from scratch (but then pay attention what you do next configuring it because the app may indeed have some bug to report). JB
Further see the error:
http://sites.google.com/site/indiadoor/firewall_error
It is showing blank. And there are no rules stored except those which come by default while enabling via gui. ...
Hi, as I suggested, a clean reset of rules database and the GUI app is sometimes better. You can do it in step 1, OR, step 2: - step 1 (GUI app only) # yum reinstall system-config-firewall and test again - step 2 (firewall base plus text UI plus GUI) # # yum reinstall system-config-firewall* and test again One more remark: when you start GUI app, just accept default rules and see if they are shown by browsing them (do not run config wizard at that time yet. Later maybe to test if that is not the cause of the trouble). JB
On Fri, Jul 23, 2010 at 1:39 PM, JB jb.123abc@yahoo.com wrote:
Hi, as I suggested, a clean reset of rules database and the GUI app is sometimes better. You can do it in step 1, OR, step 2:
- step 1 (GUI app only)
# yum reinstall system-config-firewall and test again
Run the command: yum reinstall system-config-firewall (via root)
But nothing happened, the same problem is there. http://sites.google.com/site/indiadoor/firewall_error
- step 2 (firewall base plus text UI plus GUI)
# # yum reinstall system-config-firewall* and test again
Run the command: yum reinstall system-config-firewall* (via root) But nothing happened, the same problem is there.
One more remark: when you start GUI app, just accept default rules and see if they are shown by browsing them (do not run config wizard at that time yet. Later maybe to test if that is not the cause of the trouble).
Earlier also when I installed only the default rules only, I accepted. But still the problem is remaining!!
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
... Earlier also when I installed only the default rules only, I accepted. But still the problem is remaining!!
Regards, Parshwa Murdia
Hi, some sanity checks (I am on Fedora 13; it is up to date): root@localhost jb]# ls -al /etc/sysconfig/ip*tables -rw-------. 1 root root 416 Jul 23 13:52 /etc/sysconfig/ip6tables -rw-------. 1 root root 411 Jul 23 13:52 /etc/sysconfig/iptables
[root@localhost jb]# cat /etc/sysconfig/ip*tables # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
# [root@localhost jb]# yum list *system-config-firewall* Loaded plugins: fastestmirror, langpacks, presto, priorities, protect-packages, : refresh-packagekit ... Installed Packages system-config-firewall.noarch 1.2.25-1.fc13 @updates-testing system-config-firewall-base.noarch 1.2.25-1.fc13 @updates-testing system-config-firewall-tui.noarch 1.2.25-1.fc13 @updates-testing
I played with the wizard and all is OK (that may mean only that I did not hit the "soft" spot ...). Whatever you do with with it, pay attention to every step becuase there must be some clue, if it happens during rules editing of course. JB
On Fri, Jul 23, 2010 at 6:11 PM, JB jb.123abc@yahoo.com wrote:
some sanity checks (I am on Fedora 13; it is up to date): root@localhost jb]# ls -al /etc/sysconfig/ip*tables -rw-------. 1 root root 416 Jul 23 13:52 /etc/sysconfig/ip6tables -rw-------. 1 root root 411 Jul 23 13:52 /etc/sysconfig/iptables
My results for the command:
[root@localhost ~]# ls -al /etc/sysconfig/ip*tables
is:
-rw-------. 1 root root 784 2010-07-07 14:40 /etc/sysconfig/ip6tables -rw-------. 1 root root 742 2010-07-07 14:40 /etc/sysconfig/iptables
[root@localhost jb]# cat /etc/sysconfig/ip*tables # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
For this command,
[root@localhost ~]# cat /etc/sysconfig/ip*tables
the result is,
# Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m ipv6header --header ah -j ACCEPT -A INPUT -m ipv6header --header esp -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 5353 -d ff02::fb -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 631 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p ah -j ACCEPT -A INPUT -p esp -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 631 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
# [root@localhost jb]# yum list *system-config-firewall* Loaded plugins: fastestmirror, langpacks, presto, priorities, protect-packages, : refresh-packagekit ... Installed Packages system-config-firewall.noarch 1.2.25-1.fc13 @updates-testing system-config-firewall-base.noarch 1.2.25-1.fc13 @updates-testing system-config-firewall-tui.noarch 1.2.25-1.fc13 @updates-testing
For the following command,
[root@localhost ~]# yum list *system-config-firewall*
the result is,
Loaded plugins: protectbase, refresh-packagekit 0 packages excluded due to repository protections Installed Packages system-config-firewall.noarch 1.2.16-3.fc11 @updates system-config-firewall-tui.noarch 1.2.16-3.fc11 @updates You have new mail in /var/spool/mail/root
Don't know what could be the error!
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
... [root <at> localhost ~]# cat /etc/sysconfig/ip*tables
the result is,
# Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m ipv6header --header ah -j ACCEPT -A INPUT -m ipv6header --header esp -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 5353 -d ff02::fb -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 631 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p ah -j ACCEPT -A INPUT -p esp -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 631 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
Hi, assuming that the python apps are not screwd up (you have reinstalled them ...) and their dependencies (other packages) are OK, there is something like this that should be done. Note that you have rules added to default rules (I assume thru GUI, but it really does not matter here), which can be recreated later on easily (we have them documented/saved here). So, we will reset the rules to default only (I have done it on my system - no worry, it can be restored without a problem).
Please exit your firewall app (GUI).
You should have a firewall dir like this: [root@localhost jb]# ls -al /etc/sysconfig/ip* -rw------- 1 root root 481 Jul 23 16:52 /etc/sysconfig/ip6tables -rw------- 1 root root 1753 Apr 8 12:29 /etc/sysconfig/ip6tables-config -rw------- 1 root root 416 Jul 23 14:54 /etc/sysconfig/ip6tables.old -rw------- 1 root root 476 Jul 23 16:52 /etc/sysconfig/iptables -rw------- 1 root root 1740 Apr 8 12:29 /etc/sysconfig/iptables-config -rw------- 1 root root 411 Jul 23 14:54 /etc/sysconfig/iptables.old
Let's save old rules: [root@localhost jb]# mv /etc/sysconfig/iptables.old /etc/sysconfig/iptables.old.saved [root@localhost jb]# mv /etc/sysconfig/ip6tables.old /etc/sysconfig/ip6tables.old.saved
Let's save current rules: [root@localhost jb]# mv /etc/sysconfig/iptables /etc/sysconfig/iptables.saved [root@localhost jb]# mv /etc/sysconfig/ip6tables /etc/sysconfig/ip6tables.saved
We have no rules files now.
Plase start firewall: System-Administration-Firewall . Close the startup window, input root password, and you will be greeted with a warning that the firewall is in inconsistent state and that you should create/accept new rules. You will see 2-panel screen with the usual rules items. You see them, do you ? If not we are already in a big doodoo ... It works on my system !
Please click on Apply button under the menu and confirm OK. See that the rules files were recreated. [root@localhost jb]# ls -al /etc/sysconfig/ip*tables -rw------- 1 root root 481 Jul 23 17:22 /etc/sysconfig/ip6tables -rw------- 1 root root 476 Jul 23 17:22 /etc/sysconfig/iptables
They have default rules only. [root@localhost jb]# cat /etc/sysconfig/ip*tables # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p ipv6-icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp6-adm-prohibited -A FORWARD -j REJECT --reject-with icmp6-adm-prohibited COMMIT # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT
Close firewall GUI. Restart the firewall GUI as before (System-...). You should be OK with all rules items panels editable. Are you ?
If so, then now would be the hard part - you would recreate the additional rules by adding them one at a time, saving rules (Apply button), closing and restarting firewall GUI. We want to debug it and figure out what caused the problem, right ? Good luck and let us know the intermediate and final result. JB
On Fri, Jul 23, 2010 at 9:08 PM, JB jb.123abc@yahoo.com wrote:
Parshwa Murdia <b330bkn <at> gmail.com> writes:
Please exit your firewall app (GUI).
You should have a firewall dir like this: [root@localhost jb]# ls -al /etc/sysconfig/ip*
[snip]
The output of the command: [root@localhost ~]# ls -al /etc/sysconfig/ip* is: -rw-------. 1 root root 784 2010-07-07 14:40 /etc/sysconfig/ip6tables -rw-------. 1 root root 1776 2010-07-07 14:40 /etc/sysconfig/ip6tables-config -rw-------. 1 root root 1753 2009-03-30 18:34 /etc/sysconfig/ip6tables-config.old -rw-------. 1 root root 481 2010-07-06 16:52 /etc/sysconfig/ip6tables.old -rw-------. 1 root root 742 2010-07-07 14:40 /etc/sysconfig/iptables -rw-------. 1 root root 1763 2010-07-07 14:40 /etc/sysconfig/iptables-config -rw-------. 1 root root 1740 2009-03-30 18:34 /etc/sysconfig/iptables-config.old -rw-------. 1 root root 476 2010-07-06 16:52 /etc/sysconfig/iptables.old
Let's save old rules: [root@localhost jb]# mv /etc/sysconfig/iptables.old /etc/sysconfig/iptables.old.saved [root@localhost jb]# mv /etc/sysconfig/ip6tables.old /etc/sysconfig/ip6tables.old.saved
Run both the two commands. [root@localhost ~]# mv /etc/sysconfig/iptables.old /etc/sysconfig/iptables.old.saved [root@localhost ~]# mv /etc/sysconfig/ip6tables.old /etc/sysconfig/ip6tables.old.saved
Let's save current rules: [root@localhost jb]# mv /etc/sysconfig/iptables /etc/sysconfig/iptables.saved [root@localhost jb]# mv /etc/sysconfig/ip6tables /etc/sysconfig/ip6tables.saved
Saved like this: [root@localhost ~]# mv /etc/sysconfig/iptables /etc/sysconfig/iptables.saved [root@localhost ~]# mv /etc/sysconfig/ip6tables /etc/sysconfig/ip6tables.saved
We have no rules files now. Plase start firewall: System-Administration-Firewall .
Restarted the Firewall from there after providing the root credentials, but frankly speaking, there is the same screen without any warning message.
Close the startup window, input root password, and you will be greeted with a warning that the firewall is in inconsistent state and that you should create/accept new rules. You will see 2-panel screen with the usual rules items. You see them, do you ? If not we are already in a big doodoo ... It works on my system !
No warning message here!! The same blank screen of the firewall!!
Please click on Apply button under the menu and confirm OK. See that the rules files were recreated. [root@localhost jb]# ls -al /etc/sysconfig/ip*tables -rw------- 1 root root 481 Jul 23 17:22 /etc/sysconfig/ip6tables
[snip]
So how to proceed? So at last I again did the following:
[root@localhost ~]# mv /etc/sysconfig/iptables.old.saved /etc/sysconfig/iptables.old [root@localhost ~]# mv /etc/sysconfig/ip6tables.old.saved /etc/sysconfig/ip6tables.old
And also,
[root@localhost ~]# mv /etc/sysconfig/iptables.saved /etc/sysconfig/iptables [root@localhost ~]# mv /etc/sysconfig/ip6tables.saved /etc/sysconfig/ip6tables
To undo the previous commands, its really amazing why is this happening?
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
... Restarted the Firewall from there after providing the root credentials, but frankly speaking, there is the same screen without any warning message.
Close the startup window, input root password, and you will be greeted with a warning that the firewall is in inconsistent state and that you should create/accept new rules. You will see 2-panel screen with the usual rules items. You see them, do you ? If not we are already in a big doodoo ... It works on my system !
No warning message here!! The same blank screen of the firewall!!
Well, it is Fedora 11 what you got ... As I said I have done it all on my F13 and all worked as described. At least under F13, the default rules are regenerated by the python app, filed in iptables and ip6tables files, and then formatted for display (I looked up the source code). So it is the python app system-config-firewall that fails. I can not do anything beyond what I have suggested to check. You can contact Red Hat developer directly and ask him (he should know it). Good luck. JB
On Fri, Jul 23, 2010 at 10:46 PM, JB jb.123abc@yahoo.com wrote:
Well, it is Fedora 11 what you got ... As I said I have done it all on my F13 and all worked as described. At least under F13, the default rules are regenerated by the python app, filed in iptables and ip6tables files, and then formatted for display (I looked up the source code).
Okay.
So it is the python app system-config-firewall that fails.
I didn't know this.
I can not do anything beyond what I have suggested to check.
No probs, I am also trying.
Good luck.
Thanks.
Regards, Parshwa Murdia
Parshwa Murdia <b330bkn <at> gmail.com> writes:
...
So it is the python app system-config-firewall that fails.
Well, I installed a fresh F11, it is up to date. Everything I described to you throughout the thread (I worked with F13 at that time) is valid for F11 as well. The firewall is OK. As I mentioned already, the last chance is to check dependencies (packages). This is what my F11 system shows as a reference:
# yum list *system-config-firewall* Installed Packages system-config-firewall.noarch 1.2.16-3.fc11 installed system-config-firewall-tui.noarch 1.2.16-3.fc11 installed
[root@localhost jb]# yum deplist system-config-firewall ... package: system-config-firewall.noarch 1.2.16-3.fc11 dependency: pygtk2-libglade provider: pygtk2-libglade.i586 2.14.1-1.fc11 provider: pygtk2-libglade.i586 2.14.1-2.fc11 dependency: python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: config(system-config-firewall) = 1.2.16-3.fc11 provider: system-config-firewall.noarch 1.2.16-3.fc11 dependency: gtk2 >= 2.6 provider: gtk2.i586 2.16.1-4.fc11 provider: gtk2.i586 2.16.6-2.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: hicolor-icon-theme provider: hicolor-icon-theme.noarch 0.10-6 dependency: pygtk2 provider: pygtk2.i586 2.14.1-1.fc11 provider: pygtk2.i586 2.14.1-2.fc11 dependency: /bin/sh provider: bash.i586 4.0-6.fc11 provider: bash.i586 4.0-9.fc11 dependency: usermode-gtk >= 1.94 provider: usermode-gtk.i586 1.100-2 dependency: system-config-firewall-tui = 1.2.16-3.fc11 provider: system-config-firewall-tui.noarch 1.2.16-3.fc11 ...
[root@localhost jb]# yum deplist system-config-firewall-tui ... package: system-config-firewall-tui.noarch 1.2.16-3.fc11 dependency: libselinux >= 1.19.1 provider: libselinux.i586 2.0.80-1.fc11 dependency: config(system-config-firewall-tui) = 1.2.16-3.fc11 provider: system-config-firewall-tui.noarch 1.2.16-3.fc11 dependency: newt provider: newt.i586 0.52.10-3.fc11 provider: newt.i586 0.52.10-4.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: iptables >= 1.2.8 provider: iptables.i586 1.4.3.1-1.fc11 dependency: rhpl provider: rhpl.i586 0.221-1 dependency: system-config-network-tui provider: system-config-network-tui.noarch 1.5.97-1.fc11 dependency: iptables-ipv6 provider: iptables-ipv6.i586 1.4.3.1-1.fc11
If the above verification does not result in finding a discrepancy, you basically should drop your F11 installation as not trustworthy (for whatever reason: you got that iso from a funny source, perhaps you used outside repos, you could have been hacked, whatever ...). F11 has reached an end-of-life point anyway (no official support/updates) and considering that Fedora is a fast moving target with frequent releases, it is rather advantageous for all of us "fanboyz" to move on to debug the next one. JB
On Sun, Jul 25, 2010 at 11:45 PM, JB jb.123abc@yahoo.com wrote:
# yum list *system-config-firewall*
[result]
When I run this, that is,
[root@localhost ~]# yum list *system-config-firewall*
I get:
Loaded plugins: protectbase, refresh-packagekit adobe-linux-i386 | 951 B 00:00 rpmfusion-free-updates | 2.8 kB 00:00 rpmfusion-nonfree-updates | 2.8 kB 00:00 updates/metalink | 10 kB 00:00 0 packages excluded due to repository protections Installed Packages system-config-firewall.noarch 1.2.16-3.fc11 @updates system-config-firewall-tui.noarch 1.2.16-3.fc11 @updates You have new mail in /var/spool/mail/root
[root@localhost jb]# yum deplist system-config-firewall
[result]
If I run this, that is,
[root@localhost ~]# yum deplist system-config-firewall
I get:
Loaded plugins: protectbase, refresh-packagekit 0 packages excluded due to repository protections Finding dependencies: package: system-config-firewall.noarch 1.2.16-3.fc11 dependency: pygtk2-libglade provider: pygtk2-libglade.i586 2.14.1-1.fc11 provider: pygtk2-libglade.i586 2.14.1-2.fc11 dependency: python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: config(system-config-firewall) = 1.2.16-3.fc11 provider: system-config-firewall.noarch 1.2.16-3.fc11 dependency: gtk2 >= 2.6 provider: gtk2.i586 2.16.1-4.fc11 provider: gtk2.i586 2.16.6-2.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: hicolor-icon-theme provider: hicolor-icon-theme.noarch 0.10-6 dependency: pygtk2 provider: pygtk2.i586 2.14.1-1.fc11 provider: pygtk2.i586 2.14.1-2.fc11 dependency: /bin/sh provider: bash.i586 4.0-6.fc11 provider: bash.i586 4.0-9.fc11 dependency: usermode-gtk >= 1.94 provider: usermode-gtk.i586 1.100-2 dependency: system-config-firewall-tui = 1.2.16-3.fc11 provider: system-config-firewall-tui.noarch 1.2.16-3.fc11 package: system-config-firewall.noarch 1.2.16-2.fc11 dependency: pygtk2-libglade provider: pygtk2-libglade.i586 2.14.1-1.fc11 provider: pygtk2-libglade.i586 2.14.1-2.fc11 dependency: gtk2 >= 2.6 provider: gtk2.i586 2.16.1-4.fc11 provider: gtk2.i586 2.16.6-2.fc11 dependency: python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: config(system-config-firewall) = 1.2.16-2.fc11 provider: system-config-firewall.noarch 1.2.16-2.fc11 dependency: system-config-firewall-tui = 1.2.16-2.fc11 provider: system-config-firewall-tui.noarch 1.2.16-2.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: hicolor-icon-theme provider: hicolor-icon-theme.noarch 0.10-6 dependency: pygtk2 provider: pygtk2.i586 2.14.1-1.fc11 provider: pygtk2.i586 2.14.1-2.fc11 dependency: /bin/sh provider: bash.i586 4.0-6.fc11 provider: bash.i586 4.0-9.fc11 dependency: usermode-gtk >= 1.94 provider: usermode-gtk.i586 1.100-2
[root@localhost jb]# yum deplist system-config-firewall-tui
[result]
When I run this, that is,
[root@localhost ~]# yum deplist system-config-firewall-tui
I get:
Loaded plugins: protectbase, refresh-packagekit 0 packages excluded due to repository protections Finding dependencies: package: system-config-firewall-tui.noarch 1.2.16-2.fc11 dependency: libselinux >= 1.19.1 provider: libselinux.i586 2.0.80-1.fc11 dependency: newt provider: newt.i586 0.52.10-3.fc11 provider: newt.i586 0.52.10-4.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: iptables >= 1.2.8 provider: iptables.i586 1.4.3.1-1.fc11 dependency: rhpl provider: rhpl.i586 0.221-1 dependency: system-config-network-tui provider: system-config-network-tui.noarch 1.5.97-1.fc11 dependency: config(system-config-firewall-tui) = 1.2.16-2.fc11 provider: system-config-firewall-tui.noarch 1.2.16-2.fc11 dependency: iptables-ipv6 provider: iptables-ipv6.i586 1.4.3.1-1.fc11 package: system-config-firewall-tui.noarch 1.2.16-3.fc11 dependency: libselinux >= 1.19.1 provider: libselinux.i586 2.0.80-1.fc11 dependency: config(system-config-firewall-tui) = 1.2.16-3.fc11 provider: system-config-firewall-tui.noarch 1.2.16-3.fc11 dependency: newt provider: newt.i586 0.52.10-3.fc11 provider: newt.i586 0.52.10-4.fc11 dependency: /usr/bin/python provider: python.i586 2.6-7.fc11 provider: python.i586 2.6-12.fc11 dependency: iptables >= 1.2.8 provider: iptables.i586 1.4.3.1-1.fc11 dependency: rhpl provider: rhpl.i586 0.221-1 dependency: system-config-network-tui provider: system-config-network-tui.noarch 1.5.97-1.fc11 dependency: iptables-ipv6 provider: iptables-ipv6.i586 1.4.3.1-1.fc11
If the above verification does not result in finding a discrepancy, you basically should drop your F11 installation as not trustworthy (for whatever reason: you got that iso from a funny source, perhaps you used outside repos, you could have been hacked, whatever ...). F11 has reached an end-of-life point anyway (no official support/updates) and considering that Fedora is a fast moving target with frequent releases, it is rather advantageous for all of us "fanboyz" to move on to debug the next one.
Should there be any discrepancy? Or would it mean really to reinstall this fedora 11, never preffered!
On Sun, Jul 25, 2010 at 6:44 PM, Parshwa Murdia b330bkn@gmail.com wrote:
Should there be any discrepancy? Or would it mean really to reinstall this fedora 11, never preffered!
It's too bad you can't file a bug against the issue you're experiencing since Fedora 11 isn't supported anymore. Oh wait, you knew that, didn't you?
On Mon, Jul 26, 2010 at 1:41 PM, Christofer C. Bell christofer.c.bell@gmail.com wrote:
It's too bad you can't file a bug against the issue you're experiencing since Fedora 11 isn't supported anymore.
Its really sad.
Oh wait, you knew that, didn't you?
I waited, i knew that.