ifupdown (0.8.34) unstable; urgency=medium
VLAN interfaces that are marked allow-hotplug are now brought up
automatically when the parent interface is hotplugged.
-- Guus Sliepen <guus@debian.org> Fri, 25 May 2018 22:33:22 +0200
ifupdown (0.8.32) unstable; urgency=medium
Since version 0.8, ifupdown allows concurrent calls of ifup and ifdown.
While calls for the same interface will be serialized, calls for different
interfaces can run in parallel. This is especially important during boot
time, when the chance is high that multiple interfaces are being brought up
concurrently. Ensure that any if-pre/post-up/down.d scripts you use are safe
to run concurrently, as well as any pre/post-up/down commands in
/etc/network/interfaces.
-- Guus Sliepen <guus@debian.org> Wed, 04 Apr 2018 23:20:51 +0200
ifupdown (0.8.20) unstable; urgency=medium
Ifupdown now supports pattern matching for interfaces. This will help
writing /etc/network/interfaces for systems with changing interface names,
or to simplify configuration for a large number of interfaces. The details
are in the interfaces(5) manual page, and examples are provided in
/usr/share/doc/ifupdown/examples/pattern-matching.
-- Guus Sliepen <guus@debian.org> Tue, 10 Jan 2017 17:20:09 +0100
ifupdown (0.8.17) unstable; urgency=medium
Ifupdown now also configures VLANs for bridge interfaces. (Previously, the
bridge-utils package integrated with the vlan package to do this via if-up
hooks, however since bridge-utils 1.5-11 this integration has been removed.)
-- Guus Sliepen <guus@debian.org> Tue, 10 Jan 2017 17:20:09 +0100
ifupdown (0.8.1) unstable; urgency=medium
The /etc/default/networking file is now read even when systemd is used,
although its use is not recommended.
-- Guus Sliepen <guus@debian.org> Wed, 02 Dec 2015 23:25:41 +0100
ifupdown (0.8) unstable; urgency=medium
Ifupdown now comes with a systemd service file. Any options specified in
/etc/default/networking will no longer be used. If you are using
CONFIGURE_INTERFACES=no, then run "systemctl disable networking" instead.
If you are using EXCLUDE_INTERFACES, then edit /etc/network/interfaces and
remove those interfaces from any "auto" keywords.
Ifupdown will now be more strict when errors occur, and will also properly
return a non-zero exit code when (de)configuring an interface fails. Please
ensure your /etc/network/interfaces is correct and that your interfaces can
be brought up and down without errors, especially during system startup.
Ifupdown now has more fine-grained locking, allowing concurrent calls of
ifup and ifdown. It is also allowed to call ifup and ifdown from a (pre-)up
or (post-)down line from /etc/network/interfaces, as long as no recursion
occurs.
You can now use the "inherits" keyword to copy settings from another
interface stanza.
RFC 4361 DDNS support is now enabled by default for inet dhcp interfaces if
isc-dhcp-client is installed.
-- Guus Sliepen <guus@debian.org> Sun, 22 Nov 2015 21:19:44 +0100
ifupdown (0.7~rc1+experimental) experimental; urgency=low
The --all option to ifup and ifquery can now be combined with the
--allow option to act on all interfaces of a specific class (still
defaulting to the class 'auto'). If you have custom hook scripts, you
may need to update them. See interfaces(5) for details.
-- Andrew O. Shadura <bugzilla@tut.by> Tue, 17 Apr 2012 01:05:42 +0200
Generated by dwww version 1.15 on Sat May 18 08:17:51 CEST 2024.