group.of.nepali.translators team mailing list archive

[Andy Whitcroft <apw@xxxxxxxxxxxxx>]

This is occuring because fanatic is trying to bring up the newly
configured Fan Network as if it had been brought up automatically.  This
is done to bring the system into a state that is equivalent to having
had the configuration for this Fan Network at boot time.  However it
does it using an interface which appear to fanctl as a user "who knows
what they are doing", and it brings up all matching prefixes; in this
case a prefix which is purely in the file as an example/preferred
configuration.

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided
       Status: New

-- 
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:
  In Progress
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