touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Ah, thanks for confirming. This indeed applies to interfaces which
networkd configures; man systemd.network documents this quite clearly.

> Having the bridge setup tool, modify the configuration of all
potential outgoing interface to allow forwarding seems completely wrong
to me

Full ack. Such scripts should not touch the configuration of interfaces
that they didn't set up. This is unexpected, leads to race conditions,
and isn't reliable as you wrote.

Setting to wishlist for now as it's currently behaving as documented.
I'll raise this upstream and see if they are willing to change the
default to "kernel".

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

-- 
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:
  Triaged

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