Centos 7 server iptables Active: active (exited)Is firewalld the same as iptables?Fedora 16 - Iptables...

Are there any sonatas with only two sections?

Show solution to recurrence is never a square

White foam around tubeless tires

Motorola 6845 and bitwise graphics

How to make a not so good looking person more appealing?

Were any of the books mentioned in this scene from the movie Hackers real?

Do Grothendieck universes matter for an algebraic geometer?

Why was my Canon Speedlite 600EX triggering other flashes?

Was the dragon prowess intentionally downplayed in S08E04?

Smooth function that vanishes only on unit cube

Will casting a card from the graveyard with Flashback add a quest counter on Pyromancer Ascension?

Acronyms in HDD specification

How to redirect stdout to a file, and stdout+stderr to another one?

Were any toxic metals used in the International Space Station?

Is it safe to use two single-pole breakers for a 240v circuit?

Why can't I share a one use code with anyone else?

Uh oh, the propeller fell off

Is there any good reason to write "it is easy to see"?

Can a tourist shoot a gun for recreational purpose in the USA?

Is 95% of what you read in the financial press “either wrong or irrelevant?”

Given 0s on Assignments with suspected and dismissed cheating?

Is there an academic word that means "to split hairs over"?

A case where Bishop for knight isn't a good trade

Developers demotivated due to working on same project for more than 2 years



Centos 7 server iptables Active: active (exited)


Is firewalld the same as iptables?Fedora 16 - Iptables installed, but no iptables service availableWhy iptables does not fetch information from /etc/sysconfig/iptables on centOs?iptables not getting saved ? centosiptables: command not found - CentOS 5.5Debian-Jessie: How do you check iptables status?iptables are running on reboot even though firewalld and iptables service are not started. Why?Service Active but (exited)Why iptables is loaded and active ,no pid number displayed in `ps aux`?Iptables blocking remote MySQL remoteCentOS not recognizing Rackspace verbiage for saving iptables






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















When I check the iptables service status it says Active (exited) why and how do I fix it?










share|improve this question














bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 3





    Possible duplicate of Is firewalld the same as iptables?

    – Jeff Schaller
    Oct 15 '18 at 20:11











  • Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

    – webnoob
    Oct 15 '18 at 20:43













  • It’s not running because it’s been replaced, as described in the duplicate.

    – Jeff Schaller
    Oct 15 '18 at 20:49


















0















When I check the iptables service status it says Active (exited) why and how do I fix it?










share|improve this question














bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 3





    Possible duplicate of Is firewalld the same as iptables?

    – Jeff Schaller
    Oct 15 '18 at 20:11











  • Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

    – webnoob
    Oct 15 '18 at 20:43













  • It’s not running because it’s been replaced, as described in the duplicate.

    – Jeff Schaller
    Oct 15 '18 at 20:49














0












0








0








When I check the iptables service status it says Active (exited) why and how do I fix it?










share|improve this question














When I check the iptables service status it says Active (exited) why and how do I fix it?







centos iptables






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 15 '18 at 19:55









webnoobwebnoob

6




6





bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 3





    Possible duplicate of Is firewalld the same as iptables?

    – Jeff Schaller
    Oct 15 '18 at 20:11











  • Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

    – webnoob
    Oct 15 '18 at 20:43













  • It’s not running because it’s been replaced, as described in the duplicate.

    – Jeff Schaller
    Oct 15 '18 at 20:49














  • 3





    Possible duplicate of Is firewalld the same as iptables?

    – Jeff Schaller
    Oct 15 '18 at 20:11











  • Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

    – webnoob
    Oct 15 '18 at 20:43













  • It’s not running because it’s been replaced, as described in the duplicate.

    – Jeff Schaller
    Oct 15 '18 at 20:49








3




3





Possible duplicate of Is firewalld the same as iptables?

– Jeff Schaller
Oct 15 '18 at 20:11





Possible duplicate of Is firewalld the same as iptables?

– Jeff Schaller
Oct 15 '18 at 20:11













Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

– webnoob
Oct 15 '18 at 20:43







Cannot see it is a duplicate. Here the issue is iptables is not running proberly.

– webnoob
Oct 15 '18 at 20:43















It’s not running because it’s been replaced, as described in the duplicate.

– Jeff Schaller
Oct 15 '18 at 20:49





It’s not running because it’s been replaced, as described in the duplicate.

– Jeff Schaller
Oct 15 '18 at 20:49










1 Answer
1






active

oldest

votes


















0














That message is normal; there is no error nor anything to fix (unless you want to migrate to firewalld, or something). What has happened is iptables-restore has loaded the firewall rules, and then exited, because after loading the rules it does not need to stick around. This is typical for Type=oneshot services.



[root@redacted ~]# systemctl status iptables
● iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
Active: active (exited) since Thu 2018-10-04 13:14:52 UTC; 1 weeks 4 days ago
[root@redacted ~]# wc -l /etc/sysconfig/iptables
822 /etc/sysconfig/iptables
[root@redacted ~]# systemctl list-unit-files | grep ipt
iptables.service enabled
[root@redacted ~]# systemctl list-unit-files | grep firew
firewalld.service disabled


If you peek at /usr/lib/systemd/system/iptables.service it's a wrapper around a shell script that (eventually) calls iptables-restore to load up the firewall rules from /etc/sysconfig/iptables.



(firewalld is something different and may or may not be involved (it is not on the above firewall those commands and their outputs were copied from))






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475653%2fcentos-7-server-iptables-active-active-exited%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    That message is normal; there is no error nor anything to fix (unless you want to migrate to firewalld, or something). What has happened is iptables-restore has loaded the firewall rules, and then exited, because after loading the rules it does not need to stick around. This is typical for Type=oneshot services.



    [root@redacted ~]# systemctl status iptables
    ● iptables.service - IPv4 firewall with iptables
    Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
    Active: active (exited) since Thu 2018-10-04 13:14:52 UTC; 1 weeks 4 days ago
    [root@redacted ~]# wc -l /etc/sysconfig/iptables
    822 /etc/sysconfig/iptables
    [root@redacted ~]# systemctl list-unit-files | grep ipt
    iptables.service enabled
    [root@redacted ~]# systemctl list-unit-files | grep firew
    firewalld.service disabled


    If you peek at /usr/lib/systemd/system/iptables.service it's a wrapper around a shell script that (eventually) calls iptables-restore to load up the firewall rules from /etc/sysconfig/iptables.



    (firewalld is something different and may or may not be involved (it is not on the above firewall those commands and their outputs were copied from))






    share|improve this answer




























      0














      That message is normal; there is no error nor anything to fix (unless you want to migrate to firewalld, or something). What has happened is iptables-restore has loaded the firewall rules, and then exited, because after loading the rules it does not need to stick around. This is typical for Type=oneshot services.



      [root@redacted ~]# systemctl status iptables
      ● iptables.service - IPv4 firewall with iptables
      Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
      Active: active (exited) since Thu 2018-10-04 13:14:52 UTC; 1 weeks 4 days ago
      [root@redacted ~]# wc -l /etc/sysconfig/iptables
      822 /etc/sysconfig/iptables
      [root@redacted ~]# systemctl list-unit-files | grep ipt
      iptables.service enabled
      [root@redacted ~]# systemctl list-unit-files | grep firew
      firewalld.service disabled


      If you peek at /usr/lib/systemd/system/iptables.service it's a wrapper around a shell script that (eventually) calls iptables-restore to load up the firewall rules from /etc/sysconfig/iptables.



      (firewalld is something different and may or may not be involved (it is not on the above firewall those commands and their outputs were copied from))






      share|improve this answer


























        0












        0








        0







        That message is normal; there is no error nor anything to fix (unless you want to migrate to firewalld, or something). What has happened is iptables-restore has loaded the firewall rules, and then exited, because after loading the rules it does not need to stick around. This is typical for Type=oneshot services.



        [root@redacted ~]# systemctl status iptables
        ● iptables.service - IPv4 firewall with iptables
        Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
        Active: active (exited) since Thu 2018-10-04 13:14:52 UTC; 1 weeks 4 days ago
        [root@redacted ~]# wc -l /etc/sysconfig/iptables
        822 /etc/sysconfig/iptables
        [root@redacted ~]# systemctl list-unit-files | grep ipt
        iptables.service enabled
        [root@redacted ~]# systemctl list-unit-files | grep firew
        firewalld.service disabled


        If you peek at /usr/lib/systemd/system/iptables.service it's a wrapper around a shell script that (eventually) calls iptables-restore to load up the firewall rules from /etc/sysconfig/iptables.



        (firewalld is something different and may or may not be involved (it is not on the above firewall those commands and their outputs were copied from))






        share|improve this answer













        That message is normal; there is no error nor anything to fix (unless you want to migrate to firewalld, or something). What has happened is iptables-restore has loaded the firewall rules, and then exited, because after loading the rules it does not need to stick around. This is typical for Type=oneshot services.



        [root@redacted ~]# systemctl status iptables
        ● iptables.service - IPv4 firewall with iptables
        Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
        Active: active (exited) since Thu 2018-10-04 13:14:52 UTC; 1 weeks 4 days ago
        [root@redacted ~]# wc -l /etc/sysconfig/iptables
        822 /etc/sysconfig/iptables
        [root@redacted ~]# systemctl list-unit-files | grep ipt
        iptables.service enabled
        [root@redacted ~]# systemctl list-unit-files | grep firew
        firewalld.service disabled


        If you peek at /usr/lib/systemd/system/iptables.service it's a wrapper around a shell script that (eventually) calls iptables-restore to load up the firewall rules from /etc/sysconfig/iptables.



        (firewalld is something different and may or may not be involved (it is not on the above firewall those commands and their outputs were copied from))







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 16 '18 at 0:24









        thrigthrig

        25.5k23559




        25.5k23559






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475653%2fcentos-7-server-iptables-active-active-exited%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown