No description
Find a file
Ariadne Conill 58816712c6
Merge pull request #7 from BarbarossaTM/deduce-use
Deduce which addons to 'use' from parameters names
2020-07-28 17:50:32 -04:00
.github/workflows implement a CI attempt 2020-07-19 06:03:08 -06:00
cmd lifecycle: add support for learning dependents from executors (ref #5) 2020-07-28 13:46:25 -06:00
doc ifupdown: add --force for compatibility with busybox ifupdown 2020-07-28 08:23:58 -06:00
executor-scripts/linux executors: port @ncopa's bridge scripts to run as a native executor 2020-07-28 08:34:20 -06:00
libifupdown Merge pull request #7 from BarbarossaTM/deduce-use 2020-07-28 17:50:32 -04:00
tests tests: add ifup/ifdown tests for learned dependencies (close #5) 2020-07-28 14:04:27 -06:00
.gitignore update gitignore 2020-07-24 07:48:50 -06:00
CODE_OF_CONDUCT.md add code of conduct 2020-07-18 04:51:25 -06:00
COPYING initial commit 2020-07-18 01:17:51 -06:00
Kyuafile tests: start working on testing capabilities 2020-07-18 19:46:32 -06:00
Makefile Add comparator wrapper and type cast values properly. 2020-07-28 22:44:42 +02:00
README.md fix README formatting 2020-07-25 01:18:03 -06:00

ifupdown-ng

ifupdown-ng is a network device manager that is largely compatible with Debian ifupdown, BusyBox ifupdown and Cumulus Networks' ifupdown2.

Dependency Resolution

Dependency resolution example

ifupdown-ng uses a dependency resolver to determine interface bring-up order in a deterministic way. To use this feature, you must declare relationships between interfaces with the requires keyword. This keeps the implementation efficient. For convenience, the requires keyword is exported to executors as the IF_REQUIRES environment variable.

For compatibility with some legacy ifupdown executors, we also provide the requires keyword under other environment variables in some cases.

Caveats

  • ifupdown2 python plugins are not supported at this time. An executor could be written to handle them.

  • ifupdown-ng retains compatibility with /etc/network/if-X.d scripts, but will prefer using executors in /usr/libexec/ifupdown-ng where appropriate.

Building

On musl systems, simply do make and make install to build and install.

On glibc systems, you must additionally define LIBBSD_CFLAGS and LIBBSD_LIBS:

export LIBBSD_CFLAGS=$(pkg-config --cflags libbsd-overlay)
export LIBBSD_LIBS=$(pkg-config --libs libbsd-overlay)
make
make install

To run the tests, do make check.

To build the documentation, do make docs and make install_docs. Building the documentation requires scdoc (apk add scdoc).