touch-packages team mailing list archive

[Stéphane Graber <stgraber@xxxxxxxxxxxx>]

Oh, then maybe it's only on networkd managed interfaces.

The case I saw was on Mike MacCracken's machine where he had a basic
dhcp config for eth0 which would then lead networkd to set
/proc/sys/net/ipv4/conf/eth0/forwarding to off and IIRC same happened to
/proc/sys/net/ipv6/conf/eth0/forwarding

So to clarify, I'd expect that unless I explictly turn off IPForward in
networkd's config that it doesn't go and alter the interface state and
instead leaves it at the default value set by the kernel.

This means that we can then set /proc/sys/net/ipv4/ip_forward to 1 and
get the expected behavior (which is what most scripts, firewalls, ...
do).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1500992

Title:
  networkd: Don't reset forwarding unless told to do so in config

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  It's been reported by several LXC users that systemd-networkd will
  turn off per-interface forwarding for all network interfaces when it
  starts.

  Presumably upstream expects users to go and manually edit their config
  to allow it when needed.

  This breaks LXC, libvirt, ... anything which ships a bridge that then
  NAT or route outgoing traffic. Requiring the user to do the config
  change would be a massive regression in user friendliness and having
  lxc, libvirt, ... do it for the user would be a policy violation.

  As a result, I'd recommend we patch systemd to not interfere with
  forwarding unless explicitly configured by the user. This will allow
  all our existing scripts to keep setting things up themselves and have
  it all run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500992/+subscriptions