No description
Find a file
2020-09-14 17:34:44 -06:00
.github/workflows github: add kyua debug 2020-08-24 03:32:56 -06:00
cmd multicall: load config file data as early as possible 2020-09-14 17:20:20 -06:00
dist config file: don't print warning if config file cannot be opened 2020-09-14 17:17:03 -06:00
doc ifupdown-executor man page: add create/destroy phases 2020-09-09 14:39:40 -06:00
executor-scripts Merge pull request #62 from BarbarossaTM/batman 2020-09-11 02:45:11 -06:00
libifupdown tokenizer: split out equals-as-delimiter tokenizer to its own function 2020-09-14 17:34:44 -06:00
tests tests: add test for hostname subshell 2020-09-11 02:43:32 -06:00
.gitignore ifctrstat: Initial structure for new applet 2020-08-14 11:27:43 -05: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 multicall: load config file data as early as possible 2020-09-14 17:20:20 -06:00
README.md README: link to admin guide 2020-08-18 15:26:14 -06:00

ifupdown-ng

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

For more information read the admin guide.

Dependency Resolution

Dependency resolution example

ifupdown-ng uses a dependency resolver to determine interface bring-up order in a deterministic way.

This is accomplished through a combination of manual hinting using the requires keyword and dependency learning using native executors.

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).

Discussion

Discuss ifupdown-ng on IRC: irc.as7007.net #ifupdown-ng