Linux Interface Network Manager
- Free software: GNU General Public License v2
As of today (early june 2018), the preferred method to install ifupdown2, is by building the source code (as it will always install the most recent stable release). See Installing latest stable release from sources chapter.
Installing latest stable release from sources
The sources for ifupdown2 can be downloaded from the Github repo.
You can either clone the public repository:
$ git clone git://github.com/CumulusNetworks/ifupdown2
Or download the tarball:
$ curl -OL https://github.com/CumulusNetworks/ifupdown2/tarball/master
Once you have a copy of the source, you should build a deb-package and install it
$ cd ifupdown2 && git checkout master-next && make deb
The generated deb should be in the root directory (
$ dpkg -i ../ifupdown2_1.2.1_all.deb
We don't recommend using
setup.py install directly, as it's still missing systemd/init.d scripts.
This capability should be added in the near future.
You might need to manually download dependencies. Mandatory dependencies:
$ apt-get install build-essential devscripts dh-systemd fakeroot python-all python-docutils iproute2 python-ipaddr python-argcomplete python-setuptools
$ apt-get install ethtool bridge-utils python-gvgen python-mako
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions
Report bugs at https://github.com/CumulusNetworks/ifupdown2/issues.
If you are reporting a bug, please include:
- Your operating system name and version (
- Any details about your setup that might be helpful in troubleshooting.
- Content of configuration files such as
- Detailed steps to reproduce the bug.
- Debug output of the ifupdown2 command (see
ifupdown2 could always use more documentation, whether as part of the official ifupdown2 docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/CumulusNetworks/ifupdown2/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Nikhil Gajendrakumar <email@example.com>
- Maximilian Wilhelm <firstname.lastname@example.org>
- Sven Auhagen <email@example.com>
- skorpy <firstname.lastname@example.org>
- Sam Tannous <email@example.com>
- Wilson Kok <firstname.lastname@example.org>
- John Berezovik <email@example.com>
- Daniel Walton <firstname.lastname@example.org>
- Anuradha Karuppiah <email@example.com>
- Balakrishnan Raman <firstname.lastname@example.org>
- Scott Emery <email@example.com>
- Dave Olson <firstname.lastname@example.org>
- David Ahern <email@example.com>
- Jonathan Toppins <>
- Nolan Leake <firstname.lastname@example.org>
- Sergey Sudakovich <email@example.com>
- Andy Gospodarek <>
- Satish Ashok <firstname.lastname@example.org>
- Scott Laffer <email@example.com>
- Vidya Sagar Ravipati <firstname.lastname@example.org>
- Marek Grzybowski <email@example.com>
- Gaudenz Steinlin <firstname.lastname@example.org>
- Nigel Kukard <email@example.com>
- Jeffrey <firstname.lastname@example.org>
- kokel <email@example.com>
Why not you too? :)
See changelog here: https://github.com/CumulusNetworks/ifupdown2/blob/master/debian/changelog