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

[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 systemd-networkd, but from the
> manpage, it states that this switch is important. And that it is
> important irrespective of the standard means through which we've all
> been enabling IP Forwarding in Linux so far.

Note that this has been changed/fixed in the upcoming 228. networkd
now does not disable forwarding any more if/when IPForward= is not
given, but merely enables it when it's explicitly set to "yes".
Otherwise the kernel default now applies again, which means that tools
which enable it globally will work again.

I brought this up a while ago on the ML:

  http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2015-October/008997.html

but I'm glad that we now don't have to do this any more as 228 will
fix this more sensibly.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151117/d319fad1/attachment-0002.sig>