Re: [systemd-devel] [215] bridge with static network does not work
On Fri, Oct 24, 2014 at 6:17 PM, Gerardo Exequiel Pozzi vmlinuz...@gmail.com wrote: 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. [...] 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 for the follow up. This was likely fixed by http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30313a3d5794472c3548d7288e306a5492030370. Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [215] bridge with static network does not work
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
Re: [systemd-devel] [215] bridge with static network does not work
Hi Gerardo, 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. 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)? Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [215] bridge with static network does not work
On 07/29/2014 06:24 PM, Gerardo Exequiel Pozzi wrote: Hello, Setting up a bridge with systemd-networkd does not works for me. Doing things manually works. (no network, can not ping other hosts). Output of ip addr looks same in both cases. I am sure that I am doing things correctly, if not please let me know. Thanks. By the way, If after start networkd, I set br0 to promisc executing ip link set br0 promisc on, network works fine, but of course now br0 shows PROMISC under ip link. systemd-networkd config looks like: # cat br0.netdev [NetDev] Name=br0 Kind=bridge # cat br0.network [Match] Name=br0 [Network] Address=192.168.0.77/24 Gateway=192.168.0.1 # cat enp0s16.network [Match] Name=enp0s16 [Network] Bridge=br0 and manual commands for the same (works): ip link add name br0 type bridge ip addr add 192.168.0.77/24 broadcast + dev br0 ip link set dev enp0s16 master br0 ip link set dev br0 up ip link set dev enp0s16 up ip route add default via 192.168.0.1 In both cases the output of ip addr is: 2: enp0s16: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 00:17:31:bb:44:19 brd ff:ff:ff:ff:ff:ff inet6 fe80::217:31ff:febb:4419/64 scope link valid_lft forever preferred_lft forever 8: br0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state UP group default link/ether 00:17:31:bb:44:19 brd ff:ff:ff:ff:ff:ff inet 192.168.0.77/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::217:31ff:febb:4419/64 scope link valid_lft forever preferred_lft forever and bridge fdb: 01:00:5e:00:00:01 dev enp0s16 self permanent 33:33:00:00:00:01 dev enp0s16 self permanent 33:33:ff:bb:44:19 dev enp0s16 self permanent 00:19:3e:ea:c5:54 dev enp0s16 vlan 0 00:21:29:98:d4:f3 dev enp0s16 vlan 0 00:17:31:bb:44:19 dev enp0s16 vlan 0 permanent Have a nice day! signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
