A recent change (upgrade ?) in my setup broke the network in my container.
Network is OK on the host, but not on the container.
My setup:
Host: Archlinux -
% systemctl --version
systemd 231
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master br0 state UP group default qlen 1000
link/ether 14:da:e9:b5:7a:88 brd ff:ff:ff:ff:ff:ff
3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether b6:0c:00:22:f1:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.87/24 brd 192.168.1.255 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::b40c:ff:fe22:f14a/64 scope link
valid_lft forever preferred_lft forever
5: ve-poppy@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 0e:9a:d7:18:a3:59 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 169.254.92.184/16 brd 169.254.255.255 scope link ve-poppy
valid_lft forever preferred_lft forever
inet 10.0.0.1/28 brd 10.0.0.15 scope global ve-poppy
valid_lft forever preferred_lft forever
inet 10.0.0.17/28 brd 10.0.0.31 scope global ve-poppy
valid_lft forever preferred_lft forever
inet6 fe80::c9a:d7ff:fe18:a359/64 scope link
valid_lft forever preferred_lft forever
% networkctl status
● State: routable
Address: 192.168.1.87 on br0
172.17.0.1 on docker0
10.0.0.1 on ve-poppy
10.0.0.17 on ve-poppy
169.254.92.184 on ve-poppy
fe80::b40c:ff:fe22:f14a on br0
fe80::c9a:d7ff:fe18:a359 on ve-poppy
Gateway: 192.168.1.254 (Technicolor) on br0
DNS: 192.168.1.254
------------------------------------------------------------------------------
Container: Fedora 24 -
% systemctl --version
systemd 229
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
% ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: host0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 0e:7f:c3:fb:25:b1 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.1.94/24 brd 192.168.1.255 scope global host0
valid_lft forever preferred_lft forever
inet6 fe80::c7f:c3ff:fefb:25b1/64 scope link
valid_lft forever preferred_lft forever
% networkctl status
● State: routable
Address: 192.168.1.94 on host0
fe80::c7f:c3ff:fefb:25b1 on host0
Gateway: 192.168.1.254 on host0
DNS: 192.168.1.254
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
>From 192.168.1.94 icmp_seq=1 Destination Host Unreachable
>From 192.168.1.94 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.94 icmp_seq=3 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4008ms
pipe 4
-------------------------------------------------------------
Container is started at boot this way: systemd-nspawn@poppy
Network is managed on both OS only by systemd-networkd
/etc/systemd/network/bridge.netdev
------------------------------------------------------
[NetDev]
Name=br0
Kind=bridge
/etc/systemd/network/bridge.network
----------------------------------------------------------
[Match]
Name=br0
[Network]
Address=192.168.1.87/24
Description="Dole - Poppy bridge network"
Gateway=192.168.1.254
DNS=192.168.1.254
/etc/systemd/network/eth.network
--------------------------------------------------
[Match]
Name=enp7s0
[Network]
Description="Dole - Static network with bridge"
Bridge=br0
May some one help me in debugging my issue as I can't see any reason for
this suden issue.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
