On 10/23/2014 02:06 PM, Tom Gundersen wrote: > Hi Gerardo, Hola Tom!
> > Sorry to dig up this old thread. Are you incidentally able to > reproduce this with current systemd/kernel? I am not able to on this > end. I just upgrade from 3.10.58 to 3.14.22 and with later the problem seems fixed. Using systemd-216. > > FWIW, what I do is create bridge0 with networkd and set up a DHCP > server on it, and start two containers with --network-bridge=bridge0. > These containers can then reach eachother's IP addresses just fine. > > Did you do something differently? Are you able to observe any > differences in the networkd created bridge and the brctl created one > (according to the brctl output)? > A bit different, just in real hardware: static ip to br0 and attached network card to br0. $ cat /etc/systemd/network/br0.netdev [NetDev] Name=br0 Kind=bridge $ cat /etc/systemd/network/br0.network [Match] Name=br0 [Network] Address=192.168.0.77/24 Gateway=192.168.0.1 $ cat /etc/systemd/network/enp0s16.network [Match] Name=enp0s16 [Network] Bridge=br0 In four cases (3.10.58 X 3.14.22) X (ip/brctl X networkd), the difference is the macaddr of br0 as said in [#1], but now with linux-3.14, even with a macaddr(br0) != macaddr(enp0s16) works fine. Thanks. [#1] https://bugs.freedesktop.org/show_bug.cgi?id=81979#c2 > Cheers, > > Tom >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
