This bug was fixed in the package ubuntu-fan - 0.12.4~17.04.1 --------------- ubuntu-fan (0.12.4~17.04.1) zesty; urgency=medium
[ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP: #1707610) * fanatic: recast advanced commands as non-interactive (LP: #1714966) * fanatic: fix spelling in primary help (LP: #1714966) * fanatic: fix references to fanatic manual page (LP: #1714966) [ Stefan Bader ] * fanatic: Fix typo in progress output (LP: #1714966) * README: Refresh documentation (LP: #1714966) * fanctl.8: Refresh documentation (LP: #1714966) * fanatic.8: Refresh documentation (LP: #1714966) * fanatic.8: Reword advanced to non-interactive usage (LP: #1714966) * DEP8: lxd: Suppress stderr on profile list (LP: #1714969) -- Stefan Bader <stefan.ba...@canonical.com> Fri, 18 Aug 2017 14:34:47 +0200 ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1707610 Title: fanctl does not stop setup on first match Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Triaged Status in ubuntu-fan source package in Zesty: Fix Released Bug description: SRU Justification (Zesty/Xenial) Impact: When /etc/network/fan contains two entries for the same mapping (for example on mapping for the generic network mapping and one for a specific interface) it will try to set up the same Fan bridge twice. Fix: Modify fanctl to only bring up enabled networks in auto mode and to correctly apply the most specific local configuration. Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, and host has for example a 192.168.1.0/24 address. Then trying to use fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8 would show an error now and with the fix applied work ok. Regression Potential: We tested both cases of using an underlay/overlay combination which is in the template section and one that was using a subset for the underlay. The former was working before the latter not. For that reason we anticipate a low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp