Ifupdown-ng: Difference between revisions
Prabuanand (talk | contribs) m (added link to vxlan) |
Prabuanand (talk | contribs) (added wikilink) |
||
Line 1: | Line 1: | ||
[https://github.com/ifupdown-ng/ifupdown-ng ifupdown-ng] is a network device manager which is backwards compatible with traditional ifup and ifdown as used on Debian and Alpine systems, while solving many design deficits with the original approach through robust error handling and the use of a dependency-solver to determine interface bring-up order. | [https://github.com/ifupdown-ng/ifupdown-ng ifupdown-ng] is a [[Configure Networking| network device manager]] which is backwards compatible with traditional ifup and ifdown as used on Debian and Alpine Linux systems, while solving many design deficits with the original approach through robust error handling and the use of a dependency-solver to determine interface bring-up order. | ||
== Installation == | == Installation == | ||
Line 8: | Line 8: | ||
ifupdown-ng supports {{ic|udhcpc}} from [[BusyBox]], {{pkg|dhcpcd}} and dhclient. Of these, only dhcpcd can interact with both DHCP and DHCPv6 from the same process, which ifupdown-ng requires. Thus the IPv4 DHCP configuration given on this page will also result in the use of DHCPv6, but only if the {{pkg|dhcpcd}} package is installed. The ifupdown-ng scripts prioritize dhcpcd over udhcpc as per {{path|/usr/libexec/ifupdown-ng/dhcp}} script. | ifupdown-ng supports {{ic|udhcpc}} from [[BusyBox]], {{pkg|dhcpcd}} and dhclient. Of these, only dhcpcd can interact with both DHCP and DHCPv6 from the same process, which ifupdown-ng requires. Thus the IPv4 DHCP configuration given on this page will also result in the use of DHCPv6, but only if the {{pkg|dhcpcd}} package is installed. The ifupdown-ng scripts prioritize dhcpcd over udhcpc as per {{path|/usr/libexec/ifupdown-ng/dhcp}} script. | ||
{{Note|The {{pkg|dhclient}} package is no longer available in Alpine Linux since [[Release_Notes_for_Alpine_3.21.0#ISC_DHCP|v3.21]]}} | {{Note|The {{pkg|dhclient}} package is no longer available in Alpine Linux since [[Release_Notes_for_Alpine_3.21.0#ISC_DHCP|v3.21]]}} | ||
Line 16: | Line 17: | ||
* [[Configure Networking|Main Networking page]] | * [[Configure Networking|Main Networking page]] | ||
* [https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/ADMIN-GUIDE.md ifupdown-ng Admin Guide] | * [https://github.com/ifupdown-ng/ifupdown-ng/blob/main/doc/ADMIN-GUIDE.md ifupdown-ng Admin Guide] | ||
[[Category:Networking]] | [[Category:Networking]] |
Latest revision as of 16:56, 3 June 2025
ifupdown-ng is a network device manager which is backwards compatible with traditional ifup and ifdown as used on Debian and Alpine Linux systems, while solving many design deficits with the original approach through robust error handling and the use of a dependency-solver to determine interface bring-up order.
Installation
The ifupdown-ng package is installed as part of alpine-base package and provides necessary tools for managing network configuration in Alpine Linux.
DHCP support
ifupdown-ng supports udhcpc
from BusyBox, dhcpcd and dhclient. Of these, only dhcpcd can interact with both DHCP and DHCPv6 from the same process, which ifupdown-ng requires. Thus the IPv4 DHCP configuration given on this page will also result in the use of DHCPv6, but only if the dhcpcd package is installed. The ifupdown-ng scripts prioritize dhcpcd over udhcpc as per /usr/libexec/ifupdown-ng/dhcp script.
The availability of ifupdown-ng package can be checked via the command ifquery --version
.