group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1707610] Re: fanctl does not stop setup on first match

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1707610@xxxxxxxxxxxxxxxxxx>
Date: Fri, 18 Aug 2017 18:01:55 -0000
Reply-to: Bug 1707610 <1707610@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package ubuntu-fan - 0.12.4

---------------
ubuntu-fan (0.12.4) artful; 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
  * fanatic: fix spelling in primary help
  * fanatic: fix references to fanatic manual page

  [ Stefan Bader ]
  * fanatic: Fix typo in progress output
  * README: Refresh documentation
  * fanctl.8: Refresh documentation
  * fanatic.8: Refresh documentation
  * fanatic.8: Reword advanced to non-interactive usage
  * DEP8: lxd: Suppress stderr on profile list

 -- Stefan Bader <stefan.bader@xxxxxxxxxxxxx>  Wed, 16 Aug 2017 15:58:46
+0200

** Changed in: ubuntu-fan (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  New
Status in ubuntu-fan source package in Zesty:
  New

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: Add a break which exits the setup loop once there has been one
  successful run.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+subscriptions