Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-17 Thread Martin Pitt
Ritesh Raj Sarraf [2015-11-14 15:18 +0530]: > > > IPForward=yes > > > > I believe this is the problem. Because we do not enable iptables > > support in networkd, then it cannot set this flag. This should be unrelated. This is a sysctl, not iptables. > I am not sure on how this works in

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-17 Thread Ritesh Raj Sarraf
Thanks Martin. For the issue in itself, it now looks like something specific to systemd. I'll see if I can take it up with upstream devs. Thanks, Ritesh On Tue, 2015-11-17 at 17:44 +0100, Martin Pitt wrote: > Ritesh Raj Sarraf [2015-11-14 15:18 +0530]: > > > > IPForward=yes > > > > > > I

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-14 Thread Ritesh Raj Sarraf
On Sat, 2015-11-14 at 15:18 +0530, Ritesh Raj Sarraf wrote: > That said, it still does not work. And the odd part is, networking is > only broken for IPv4. From within the container, this reporting from networkctl is interesting. It states: root@deb-template:~# networkctl status ●  State:

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-14 Thread Ritesh Raj Sarraf
Hello Felipe, On Thu, 2015-11-12 at 10:02 -0300, Felipe Sateler wrote: > rrs@chutzpah:~$ cat /etc/systemd/network/localBridge.network > > [Match] > > Name=sysbr0 > > > > [Network] > > DHCPServer=yes > > IPForward=yes > > I believe this is the problem. Because we do not enable iptables >

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-14 Thread Ritesh Raj Sarraf
On Thu, 2015-11-12 at 10:02 -0300, Felipe Sateler wrote: > I believe this is the problem. Because we do not enable iptables > support in networkd, then it cannot set this flag. > > I'd love to have iptables support enabled, but upstream wants to > switch to nftables at some point. Switch costs

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-14 Thread Ritesh Raj Sarraf
On Sat, 2015-11-14 at 15:27 +0530, Ritesh Raj Sarraf wrote: > > I am not sure how it determines the "routable" status. The default > gateway is 172.16.20.1, which is not pingable. The same setup, now bound to the traditional bridge, is working. root@deb-template:~# networkctl status ●  

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

2015-11-12 Thread Felipe Sateler
On 12 November 2015 at 04:09, Ritesh Raj Sarraf wrote: > Package: systemd > Version: 227-2 > Severity: normal > > With the new systemd-networkd support, my intent is to explore the > possiblity of moving away from my old bridge setup, to the new setup > provided by