debian/NEWS

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