We actually only want to bring up enabled Fan Networks, fanatic is indicating this via its use of --auto. Use this to modify the config scanner.
Does the attached (untested) patch help. ** Patch added: "0001-fanctl-only-bring-up-enabled-Fan-Networks-in-auto-mo.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+attachment/4925799/+files/0001-fanctl-only-bring-up-enabled-Fan-Networks-in-auto-mo.patch -- 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: 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 -- 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
