F41 Change Proposal: Removing network-scripts package (System-Wide)

Removing network-scripts package

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.


:link: Summary

network-scripts package will be removed in Fedora 41. By removing the package, we also remove support for legacy ifup/ifdown network scripts that have been deprecated since 2018.

:link: Owner

:link: Detailed Description

network-scripts will be removed in Fedora 41. It provides legacy ifup/ifdown scripts as well as network.service.

The network-scripts were deprecated in 2018, and since then, upstream has provided only limited support.

The main reason for removing network-scripts is that ISC dhcp has not been maintained upstream since the end of 2022. There is plan to remove it upcoming Fedora release. Network scripts heavily depend on the DHCP client, and since Network Scripts are no longer developed, there is no chance of updating them to use an alternative client.

:link: Feedback

:link: Benefit to Fedora

We don’t deliver software that has been deprecated for many years, unmaintained upstream, and for which we don’t have resources to maintain downstream. Additionally, it simplifies networking tasks for users and administrators because NetworkManager will be used more uniformly across Fedora environments.

:link: Scope

  • Proposal owners: Removing of network-scripts rpm package.

  • Other developers: Make sure that dependency on network-scripts package is removed (see #Dependencies).

  • Release engineering: N/A (not needed for this Change)

  • Policies and guidelines: N/A (not needed for this Change)

  • Trademark approval: N/A (not needed for this Change)

  • Alignment with Community Initiatives: N/A (not needed for this Change)

:link: Upgrade/compatibility impact

ifup/ifdown command are no longer available. Use nmcli connection up/down or networkctl up/down instead.

Old ifcfg network configuration should still work thanks to NetworkManager-initscripts-ifcfg-rh package. No migration is needed, but it is recommended to migrate from ifcfg to keyfiles configuration.

You can use one of the following articles on how to migrate:

:link: How To Test

Networking should work as before the removal of network-scripts package.

:link: User Experience

:link: Dependencies

RPM packages that depends in some form on network-scripts:

Note that this will also affect all users with local custom network-scripts that require functionality from network-scripts package.

:link: Contingency Plan

  • Contingency mechanism: Since dhcp client is no longer maintained and is going to be deprecated in Fedora, there is currently no contingency mechanism.
  • Contingency deadline: beta freeze
  • Blocks release: No

:link: Documentation

:link: Release Notes

Last edited by @amoloney 2024-05-31T08:57:14Z


How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply giving that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.


This change proposal has now been submitted to FESCo with ticket #3221 for voting.

To find out more, please visit our Changes Policy documentation.