** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-fan (Ubuntu)
Status: Fix Committed => Invalid
--
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/1570565
Title:
fanatic fails on rpi2 running xenial
Status in linux-raspi2 package in Ubuntu:
Fix Released
Status in ubuntu-fan package in Ubuntu:
Invalid
Bug description:
ubuntu@ubuntu:~⟫ sudo apt install ubuntu-fan
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
ubuntu-fan
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 29.3 kB of archives.
After this operation, 138 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/universe armhf ubuntu-fan
all 0.9.0 [29.3 kB]
Fetched 29.3 kB in 0s (62.8 kB/s)
Selecting previously unselected package ubuntu-fan.
(Reading database ... 50432 files and directories currently installed.)
Preparing to unpack .../ubuntu-fan_0.9.0_all.deb ...
Unpacking ubuntu-fan (0.9.0) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Setting up ubuntu-fan (0.9.0) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
ubuntu@ubuntu:~⟫ sudo fanatic
Welcome to the fanatic fan networking wizard. This will help you set
up an example fan network and optionally configure docker and/or LXD to
use this network. See fanatic(1) for more details.
Configure fan underlay (hit return to accept, or specify alternative)
[10.0.0.0/16]:
Configure fan overlay (hit return to accept, or specify alternative)
[250.0.0.0/8]:
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev eth0 dstport 0
local 10.0.0.113 fan-map 250.0.0.0/8:10.
0.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
Cannot find device "ftun0"
/usr/sbin/fanctl: ip link set dev ftun0 up
/usr/sbin/fanctl: WARNING: ftun0: failed to up interface
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
interface ftun0 does not exist!
/usr/sbin/fanctl: brctl addif fan-250 ftun0
/usr/sbin/fanctl: WARNING: ftun0: failed to add vxlan interface to bridge
Cannot find device "ftun0"
Cannot find device "ftun0"
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
iptables: Chain already exists.
/usr/sbin/fanctl: iptables -t nat -N fan-egress
/usr/sbin/fanctl: WARNING: unable to initialise NAT core (new chain)
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
Cannot find device "fan-250"
/usr/sbin/fanctl: ip addr add 250.0.113.1/8 dev fan-250
/usr/sbin/fanctl: WARNING: fan-250: failed to add 250.0.113.1/8 address
iptables: Too many links.
Cannot find device "fan-250"
/usr/sbin/fanctl: ip link set dev fan-250 up
/usr/sbin/fanctl: WARNING: fan-250: failed to bring interface up
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
dnsmasq: failed to create listening socket for 250.0.113.1: Cannot assign
requested address
/usr/sbin/fanctl: dnsmasq -u dnsmasq --strict-order --bind-interfaces
--pid-file=/run/ubuntu-fan/dnsmasq-fan-250.pid -
-conf-file= --listen-address 250.0.113.1 --dhcp-range
250.0.113.2,250.0.113.254 --dhcp-no-override --except-interface=
lo --interface=fan-250 --dhcp-leasefile=/var/lib/misc/dnsmasq.fan-250.leases
--dhcp-authoritative
/usr/sbin/fanctl: WARNING: fan-250: failed to start dnsmasq
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanctl: /etc/network/fan:40 10.0.0.0/16 250.0.0.0/8 -- failed err=1
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev lxcbr0 dstport
0 local 10.0.1.1 fan-map 250.0.0.0/8:10.
0.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
Cannot find device "ftun0"
/usr/sbin/fanctl: ip link set dev ftun0 up
/usr/sbin/fanctl: WARNING: ftun0: failed to up interface
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
iptables: Chain already exists.
/usr/sbin/fanctl: iptables -t nat -N fan-egress
/usr/sbin/fanctl: WARNING: unable to initialise NAT core (new chain)
Cannot find device "ftun0"
Cannot find device "ftun0"
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Directory not empty.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
Cannot find device "fan-250"
/usr/sbin/fanctl: ip addr add 250.1.1.1/8 dev fan-250
/usr/sbin/fanctl: WARNING: fan-250: failed to add 250.1.1.1/8 address
iptables: Too many links.
Cannot find device "fan-250"
/usr/sbin/fanctl: ip link set dev fan-250 up
/usr/sbin/fanctl: WARNING: fan-250: failed to bring interface up
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
dnsmasq: failed to create listening socket for 250.1.1.1: Cannot assign
requested address
/usr/sbin/fanctl: dnsmasq -u dnsmasq --strict-order --bind-interfaces
--pid-file=/run/ubuntu-fan/dnsmasq-fan-250.pid -
-conf-file= --listen-address 250.1.1.1 --dhcp-range 250.1.1.2,250.1.1.254
--dhcp-no-override --except-interface=lo --i
nterface=fan-250 --dhcp-leasefile=/var/lib/misc/dnsmasq.fan-250.leases
--dhcp-authoritative
/usr/sbin/fanctl: WARNING: fan-250: failed to start dnsmasq
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Too many links.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanctl: /etc/network/fan:40 10.0.0.0/16 250.0.0.0/8 -- failed err=1
Create LXD networking for underlay:10.0.0.0/16 overlay:250.0.0.0/8 [Yn]: n
Create docker networking for underlay:10.0.0.0/16 overlay:250.0.0.0/8 [Yn]: n
This host IP address: 10.0.0.113
Remote test host IP address (none to skip):
/usr/sbin/fanatic: Testing skipped
ubuntu@ubuntu:~⟫
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1570565/+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
