RHEL 8 Deprecated Network Scripts

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I was reading about RHEL 8, and this statement is made:




Network scripts are deprecated in Red Hat Enterprise Linux 8 and they are no longer provided by default. The basic installation provides a new version of the ifup and ifdown scripts which call the NetworkManager service through the nmcli tool.




OK, so to me this would imply that /etc/sysconfig/network-scripts would no longer be used, though it is unclear from my reading what is supposed to replace ifcfg-eth0 (or similar).



But then I read this page about static IP addresses, which asserted:




The procedure to configure a static IP address on RHEL 8:
Create a file named /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:

DEVICE=eth0

BOOTPROTO=none

ONBOOT=yes

PREFIX=24

IPADDR=192.168.2.203



Restart network service on RHEL 8: systemctl restart NetworkManager OR sudo nmcli connection reload




So, is it only the ifup and ifdown that are deprecated, but the configuration files remain? Is the distinction between scripts and configuration files, even though they seem lumped under a single chapter? Chapter 12 of the RHEL defixed network scripts as the:




Chapter 12. Network Scripts

...configuration files for network interfaces and the scripts to activate and deactivate them are located in the /etc/sysconfig/network-scripts/ directory.




So, what constitutes what is deprecated? It doesn't seem to be the scripts in /etc/sysconfig/network-scripts since that apparently is still an appropriate way to configure a static IP.



I do not yet have a RHEL 8 box running, so I am hoping someone can shed light on what it is one is supposed to avoid.










share|improve this question



























    up vote
    1
    down vote

    favorite












    I was reading about RHEL 8, and this statement is made:




    Network scripts are deprecated in Red Hat Enterprise Linux 8 and they are no longer provided by default. The basic installation provides a new version of the ifup and ifdown scripts which call the NetworkManager service through the nmcli tool.




    OK, so to me this would imply that /etc/sysconfig/network-scripts would no longer be used, though it is unclear from my reading what is supposed to replace ifcfg-eth0 (or similar).



    But then I read this page about static IP addresses, which asserted:




    The procedure to configure a static IP address on RHEL 8:
    Create a file named /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:

    DEVICE=eth0

    BOOTPROTO=none

    ONBOOT=yes

    PREFIX=24

    IPADDR=192.168.2.203



    Restart network service on RHEL 8: systemctl restart NetworkManager OR sudo nmcli connection reload




    So, is it only the ifup and ifdown that are deprecated, but the configuration files remain? Is the distinction between scripts and configuration files, even though they seem lumped under a single chapter? Chapter 12 of the RHEL defixed network scripts as the:




    Chapter 12. Network Scripts

    ...configuration files for network interfaces and the scripts to activate and deactivate them are located in the /etc/sysconfig/network-scripts/ directory.




    So, what constitutes what is deprecated? It doesn't seem to be the scripts in /etc/sysconfig/network-scripts since that apparently is still an appropriate way to configure a static IP.



    I do not yet have a RHEL 8 box running, so I am hoping someone can shed light on what it is one is supposed to avoid.










    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I was reading about RHEL 8, and this statement is made:




      Network scripts are deprecated in Red Hat Enterprise Linux 8 and they are no longer provided by default. The basic installation provides a new version of the ifup and ifdown scripts which call the NetworkManager service through the nmcli tool.




      OK, so to me this would imply that /etc/sysconfig/network-scripts would no longer be used, though it is unclear from my reading what is supposed to replace ifcfg-eth0 (or similar).



      But then I read this page about static IP addresses, which asserted:




      The procedure to configure a static IP address on RHEL 8:
      Create a file named /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:

      DEVICE=eth0

      BOOTPROTO=none

      ONBOOT=yes

      PREFIX=24

      IPADDR=192.168.2.203



      Restart network service on RHEL 8: systemctl restart NetworkManager OR sudo nmcli connection reload




      So, is it only the ifup and ifdown that are deprecated, but the configuration files remain? Is the distinction between scripts and configuration files, even though they seem lumped under a single chapter? Chapter 12 of the RHEL defixed network scripts as the:




      Chapter 12. Network Scripts

      ...configuration files for network interfaces and the scripts to activate and deactivate them are located in the /etc/sysconfig/network-scripts/ directory.




      So, what constitutes what is deprecated? It doesn't seem to be the scripts in /etc/sysconfig/network-scripts since that apparently is still an appropriate way to configure a static IP.



      I do not yet have a RHEL 8 box running, so I am hoping someone can shed light on what it is one is supposed to avoid.










      share|improve this question















      I was reading about RHEL 8, and this statement is made:




      Network scripts are deprecated in Red Hat Enterprise Linux 8 and they are no longer provided by default. The basic installation provides a new version of the ifup and ifdown scripts which call the NetworkManager service through the nmcli tool.




      OK, so to me this would imply that /etc/sysconfig/network-scripts would no longer be used, though it is unclear from my reading what is supposed to replace ifcfg-eth0 (or similar).



      But then I read this page about static IP addresses, which asserted:




      The procedure to configure a static IP address on RHEL 8:
      Create a file named /etc/sysconfig/network-scripts/ifcfg-eth0 as follows:

      DEVICE=eth0

      BOOTPROTO=none

      ONBOOT=yes

      PREFIX=24

      IPADDR=192.168.2.203



      Restart network service on RHEL 8: systemctl restart NetworkManager OR sudo nmcli connection reload




      So, is it only the ifup and ifdown that are deprecated, but the configuration files remain? Is the distinction between scripts and configuration files, even though they seem lumped under a single chapter? Chapter 12 of the RHEL defixed network scripts as the:




      Chapter 12. Network Scripts

      ...configuration files for network interfaces and the scripts to activate and deactivate them are located in the /etc/sysconfig/network-scripts/ directory.




      So, what constitutes what is deprecated? It doesn't seem to be the scripts in /etc/sysconfig/network-scripts since that apparently is still an appropriate way to configure a static IP.



      I do not yet have a RHEL 8 box running, so I am hoping someone can shed light on what it is one is supposed to avoid.







      rhel networkmanager






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 at 6:25









      Rui F Ribeiro

      38.3k1475126




      38.3k1475126










      asked Nov 22 at 4:45









      KevinO

      5701310




      5701310




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          From your first link:




          Note that custom commands in /sbin/ifup-local, ifdown-pre-local and ifdown-local scripts are not executed.



          If any of these scripts are required, the installation of the deprecated network scripts in the system is still possible with the following command:



          ~]# yum install network-scripts



          So, anything contained in the RHEL 8 network-scripts RPM file or relying on functionality of that RPM is now deprecated. In particular, if you previously used scripts like /sbin/ifup-local to set up some advanced routing or other specialized network configuration, now it's time to find out a new way to do that.



          Note that when NetworkManager was introduced into RHEL, it included - and still does - a configuration back-end that uses the old configuration file locations, but with a new NetworkManager infrastructure and an extended version of the old configuration script syntax. So the /etc/sysconfig/network-scripts/ifcfg-* files will still be there and using the same syntax, although they will now be parsed by NetworkManager and not executed as sourced scripts.



          The deprecated network-scripts package essentially contains:



          • the SysVinit-style service script /etc/init.d/network

          • the ifup*, ifdown*, init.ipv6-global and network-functions* scripts you've used to seeing in the /etc/sysconfig/network-scripts/ directory

          • classic versions of /usr/sbin/ifup and /usr/sbin/ifdown (which would override the compatibility wrappers for nmcli that are present by default)

          • the /usr/sbin/usernetctl command

          • and the associated documentation and example files

          So, when you're not using the deprecated network-scripts RPM, you would now expect the /etc/sysconfig/network-scripts/ directory to only contain the ifcfg-* files for your network interfaces, and possibly route-* files for custom routes, but no other files at all. If you needed the usernetctl command, it's among the deprecated functionality and you should start using the appropriate nmcli subcommands as its replacement.



          ifup and ifdown will still be available, but now do their job through NetworkManager, unless you install the deprecated network-scripts RPM.






          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',
            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%2f483354%2frhel-8-deprecated-network-scripts%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








            up vote
            3
            down vote



            accepted










            From your first link:




            Note that custom commands in /sbin/ifup-local, ifdown-pre-local and ifdown-local scripts are not executed.



            If any of these scripts are required, the installation of the deprecated network scripts in the system is still possible with the following command:



            ~]# yum install network-scripts



            So, anything contained in the RHEL 8 network-scripts RPM file or relying on functionality of that RPM is now deprecated. In particular, if you previously used scripts like /sbin/ifup-local to set up some advanced routing or other specialized network configuration, now it's time to find out a new way to do that.



            Note that when NetworkManager was introduced into RHEL, it included - and still does - a configuration back-end that uses the old configuration file locations, but with a new NetworkManager infrastructure and an extended version of the old configuration script syntax. So the /etc/sysconfig/network-scripts/ifcfg-* files will still be there and using the same syntax, although they will now be parsed by NetworkManager and not executed as sourced scripts.



            The deprecated network-scripts package essentially contains:



            • the SysVinit-style service script /etc/init.d/network

            • the ifup*, ifdown*, init.ipv6-global and network-functions* scripts you've used to seeing in the /etc/sysconfig/network-scripts/ directory

            • classic versions of /usr/sbin/ifup and /usr/sbin/ifdown (which would override the compatibility wrappers for nmcli that are present by default)

            • the /usr/sbin/usernetctl command

            • and the associated documentation and example files

            So, when you're not using the deprecated network-scripts RPM, you would now expect the /etc/sysconfig/network-scripts/ directory to only contain the ifcfg-* files for your network interfaces, and possibly route-* files for custom routes, but no other files at all. If you needed the usernetctl command, it's among the deprecated functionality and you should start using the appropriate nmcli subcommands as its replacement.



            ifup and ifdown will still be available, but now do their job through NetworkManager, unless you install the deprecated network-scripts RPM.






            share|improve this answer
























              up vote
              3
              down vote



              accepted










              From your first link:




              Note that custom commands in /sbin/ifup-local, ifdown-pre-local and ifdown-local scripts are not executed.



              If any of these scripts are required, the installation of the deprecated network scripts in the system is still possible with the following command:



              ~]# yum install network-scripts



              So, anything contained in the RHEL 8 network-scripts RPM file or relying on functionality of that RPM is now deprecated. In particular, if you previously used scripts like /sbin/ifup-local to set up some advanced routing or other specialized network configuration, now it's time to find out a new way to do that.



              Note that when NetworkManager was introduced into RHEL, it included - and still does - a configuration back-end that uses the old configuration file locations, but with a new NetworkManager infrastructure and an extended version of the old configuration script syntax. So the /etc/sysconfig/network-scripts/ifcfg-* files will still be there and using the same syntax, although they will now be parsed by NetworkManager and not executed as sourced scripts.



              The deprecated network-scripts package essentially contains:



              • the SysVinit-style service script /etc/init.d/network

              • the ifup*, ifdown*, init.ipv6-global and network-functions* scripts you've used to seeing in the /etc/sysconfig/network-scripts/ directory

              • classic versions of /usr/sbin/ifup and /usr/sbin/ifdown (which would override the compatibility wrappers for nmcli that are present by default)

              • the /usr/sbin/usernetctl command

              • and the associated documentation and example files

              So, when you're not using the deprecated network-scripts RPM, you would now expect the /etc/sysconfig/network-scripts/ directory to only contain the ifcfg-* files for your network interfaces, and possibly route-* files for custom routes, but no other files at all. If you needed the usernetctl command, it's among the deprecated functionality and you should start using the appropriate nmcli subcommands as its replacement.



              ifup and ifdown will still be available, but now do their job through NetworkManager, unless you install the deprecated network-scripts RPM.






              share|improve this answer






















                up vote
                3
                down vote



                accepted







                up vote
                3
                down vote



                accepted






                From your first link:




                Note that custom commands in /sbin/ifup-local, ifdown-pre-local and ifdown-local scripts are not executed.



                If any of these scripts are required, the installation of the deprecated network scripts in the system is still possible with the following command:



                ~]# yum install network-scripts



                So, anything contained in the RHEL 8 network-scripts RPM file or relying on functionality of that RPM is now deprecated. In particular, if you previously used scripts like /sbin/ifup-local to set up some advanced routing or other specialized network configuration, now it's time to find out a new way to do that.



                Note that when NetworkManager was introduced into RHEL, it included - and still does - a configuration back-end that uses the old configuration file locations, but with a new NetworkManager infrastructure and an extended version of the old configuration script syntax. So the /etc/sysconfig/network-scripts/ifcfg-* files will still be there and using the same syntax, although they will now be parsed by NetworkManager and not executed as sourced scripts.



                The deprecated network-scripts package essentially contains:



                • the SysVinit-style service script /etc/init.d/network

                • the ifup*, ifdown*, init.ipv6-global and network-functions* scripts you've used to seeing in the /etc/sysconfig/network-scripts/ directory

                • classic versions of /usr/sbin/ifup and /usr/sbin/ifdown (which would override the compatibility wrappers for nmcli that are present by default)

                • the /usr/sbin/usernetctl command

                • and the associated documentation and example files

                So, when you're not using the deprecated network-scripts RPM, you would now expect the /etc/sysconfig/network-scripts/ directory to only contain the ifcfg-* files for your network interfaces, and possibly route-* files for custom routes, but no other files at all. If you needed the usernetctl command, it's among the deprecated functionality and you should start using the appropriate nmcli subcommands as its replacement.



                ifup and ifdown will still be available, but now do their job through NetworkManager, unless you install the deprecated network-scripts RPM.






                share|improve this answer












                From your first link:




                Note that custom commands in /sbin/ifup-local, ifdown-pre-local and ifdown-local scripts are not executed.



                If any of these scripts are required, the installation of the deprecated network scripts in the system is still possible with the following command:



                ~]# yum install network-scripts



                So, anything contained in the RHEL 8 network-scripts RPM file or relying on functionality of that RPM is now deprecated. In particular, if you previously used scripts like /sbin/ifup-local to set up some advanced routing or other specialized network configuration, now it's time to find out a new way to do that.



                Note that when NetworkManager was introduced into RHEL, it included - and still does - a configuration back-end that uses the old configuration file locations, but with a new NetworkManager infrastructure and an extended version of the old configuration script syntax. So the /etc/sysconfig/network-scripts/ifcfg-* files will still be there and using the same syntax, although they will now be parsed by NetworkManager and not executed as sourced scripts.



                The deprecated network-scripts package essentially contains:



                • the SysVinit-style service script /etc/init.d/network

                • the ifup*, ifdown*, init.ipv6-global and network-functions* scripts you've used to seeing in the /etc/sysconfig/network-scripts/ directory

                • classic versions of /usr/sbin/ifup and /usr/sbin/ifdown (which would override the compatibility wrappers for nmcli that are present by default)

                • the /usr/sbin/usernetctl command

                • and the associated documentation and example files

                So, when you're not using the deprecated network-scripts RPM, you would now expect the /etc/sysconfig/network-scripts/ directory to only contain the ifcfg-* files for your network interfaces, and possibly route-* files for custom routes, but no other files at all. If you needed the usernetctl command, it's among the deprecated functionality and you should start using the appropriate nmcli subcommands as its replacement.



                ifup and ifdown will still be available, but now do their job through NetworkManager, unless you install the deprecated network-scripts RPM.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 at 8:43









                telcoM

                14.5k11842




                14.5k11842



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f483354%2frhel-8-deprecated-network-scripts%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






                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?