top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Where is the iptables firewall configuration file on Fedora 19?

0 votes

It's no longer in /etc/sysconfig/iptables.

posted Aug 9, 2013 by Mandeep Sehgal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

2 Answers

0 votes

Mine are there...

$ sudo cat /etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.

Have you exec system-config-firewall ?

answer Aug 9, 2013 by Naveena Garg
0 votes

Fedora 19 used FirewallD by default ( If you prefer to use the iptables initscripts, you need to install iptables-services and issue 'systemctl disable firewalld'.

answer Aug 9, 2013 by Meenal Mishra
Similar Questions
+1 vote

In a previous version of Fedora I had iptables rules of the form:

-A INPUT -p tcp --destination-port 25 -m mac --mac-source  AA:BB:CC:DD:EE:FF -j ACCEPT

in order to accept email only from selected local systems.

Ive just installed Fedora 20, and Im trying to implement the same kind of thing using:


but Ive been unable to figure out how to do this. Any thoughts?

0 votes

I'm playing around with iptables and have inserted a few new rules. Now, I want to flush them all so I use

iptables -F

Then, I restart the firewall with

service iptables restart

and everything looks like it's restarting alright. But when I list the rules using

iptables -L

I get a list of rules THAT INCLUDE all of the rules I've defined before the flush! Am I reading this wrong or is something weird with my iptables?

0 votes

I have a system that I upgraded from Fedora 18 to 19 recently and I just installed eclipse, but it says that there's no JVM when I try and run it. I noticed that /usr/bin/java is a symbolic link to
/etc/alternatives/java which is then a symbolic link to
/usr/lib/jvm/jre-1.7.0-openjdk/bin/java but it's actually installed at

Is this an issue from the update from Fedora 18 to 19? Or is it an issue with the packages in Fedora 19?

0 votes

I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:

 # systemctl start transmission-daemon.service

If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.

0 votes

When I try:

 ping -R

I get:

PING ( 56(124) bytes of data.

but the list of nodes does not appear, and I wait for more than 5 minutes. traceroute gives immediately the list of nodes.

This is fedora 18, iptables stopped (and flushed), firewalld stopped.Could it be somehow due to not flushing firewalld rules ? (I don't know much about firewalld)