← Back to team overview

touch-packages team mailing list archive

[Bug 1500992] [NEW] networkd: Don't reset forwarding unless told to do so in config

 

Public bug reported:

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.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

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

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


Follow ups