No description
Find a file
2020-07-25 00:58:32 -06:00
.github/workflows implement a CI attempt 2020-07-19 06:03:08 -06:00
cmd use "use loopback" hint instead of "inet loopback", same with dhcp 2020-07-24 05:00:49 -06:00
doc add docs for ifdown/ifup/interfaces too 2020-07-24 08:28:29 -06:00
libifupdown lifecycle: add backwards compat for netmask triples 2020-07-25 00:58:32 -06:00
tests tests: add tests for use dhcp variant 2020-07-24 05:04:33 -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 ifupdown-ng 0.2.1. 2020-07-24 08:33:22 -06:00
README.md README: note how to build apps, docs and run the tests 2020-07-24 07:17:18 -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

Simply do make and make install to build and 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).