I'd like to get your confirmation that what we're seeing are the expected result and whether I need to file new bugs for 3, 4 and 5.
1. upgrading a 2.3.1 model to 2.3.2 doesn't fix LXD, neither on old nor new machines.
2. creating a new 2.3.2 model fixes LXD: the container network is now host-only (local).
3. container-networking-method=fan and fan-config=10.10.0.0/16=192.168.0.0/8 results in the error "failed to start machine 0/lxd/0 (unable to setup network: host machine "0" has no available FAN devices in space(s) ""), retrying in 10s (8 more attempts)"
4. container-networking-method=provider and an external network without IP address breaks the networking of both the host and the container.
5. container-networking-method=provider and only internal network breaks the networking of the container.
This is with "promiscuous mode", "MAC address changes" and "forged transmits" allowed. If I look at the `ifconfig` output, it seems as if there is more wrong; the `lxdbr0` interface still has `10.0.187.1` as ip; as if the container network mode is "local"..
@wpk
I'd like to get your confirmation that what we're seeing are the expected result and whether I need to file new bugs for 3, 4 and 5.
1. upgrading a 2.3.1 model to 2.3.2 doesn't fix LXD, neither on old nor new machines.
2. creating a new 2.3.2 model fixes LXD: the container network is now host-only (local).
3. container- networking- method= fan and fan-config= 10.10.0. 0/16=192. 168.0.0/ 8 results in the error "failed to start machine 0/lxd/0 (unable to setup network: host machine "0" has no available FAN devices in space(s) ""), retrying in 10s (8 more attempts)"
4. container- networking- method= provider and an external network without IP address breaks the networking of both the host and the container. networking- method= provider and only internal network breaks the networking of the container.
5. container-
This is with "promiscuous mode", "MAC address changes" and "forged transmits" allowed. If I look at the `ifconfig` output, it seems as if there is more wrong; the `lxdbr0` interface still has `10.0.187.1` as ip; as if the container network mode is "local"..
br-ens192 Link encap:Ethernet HWaddr 00:50:56:a4:15:06 56ff:fea4: 1506/64 Scope:Link
collisions: 0 txqueuelen:1000
inet addr:10.10.137.58 Bcast:10.10.139.255 Mask:255.255.252.0
inet6 addr: fe80::250:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14927 errors:0 dropped:0 overruns:0 frame:0
TX packets:11837 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:166431103 (166.4 MB) TX bytes:859619 (859.6 KB)
ens192 Link encap:Ethernet HWaddr 00:50:56:a4:15:06
collisions: 0 txqueuelen:1000
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:376714 errors:0 dropped:0 overruns:0 frame:0
TX packets:11868 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:299912573 (299.9 MB) TX bytes:868937 (868.9 KB)
lo Link encap:Local Loopback
collisions: 0 txqueuelen:1
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:11840 (11.8 KB) TX bytes:11840 (11.8 KB)
lxdbr0 Link encap:Ethernet HWaddr b6:86:6c:b0:b6:1b 6cff:feb0: b61b/64 Scope:Link
collisions: 0 txqueuelen:1000
inet addr:10.0.187.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::b486:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:570 (570.0 B)
vethB20SMK Link encap:Ethernet HWaddr fe:90:2f:2f:06:eb 2fff:fe2f: 6eb/64 Scope:Link
collisions: 0 txqueuelen:1000
inet6 addr: fe80::fc90:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:0 dropped:0 overruns:0 frame:0
TX packets:341 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:9150 (9.1 KB) TX bytes:90298 (90.2 KB)
```