Ubuntu
systemd package

  1. Bug #1727301
  2. Comment #4

Comment 4 for bug 1727301

Revision history for this message
Tobias Wolf (towolf) wrote :

We are also affected by this suddenly after systemd upgrade the network was gone, had to go in via serial console.

We are only using networkd because Martin Pitt said in the run-up to the 16.04 release that networkd would be supported and to be used in the next LTS release.

# networkctl
IDX LINK TYPE OPERATIONAL SETUP
  1 lo loopback carrier unmanaged
  2 eth0 ether carrier configured
  3 eth1 ether carrier configured
  4 eth2 ether carrier configured
  5 eth3 ether carrier configured
  6 eth4 ether no-carrier configured
  7 eth5 ether no-carrier configured
  8 bond0 ether off unmanaged
  9 bond1 ether routable configured

9 links listed.

# head /etc/systemd/network/* -n 20
==> /etc/systemd/network/bond1.netdev <==
[NetDev]
Name=bond1
Kind=bond

[Bond]
Mode=802.3ad
MIIMonitorSec=100
TransmitHashPolicy=layer3+4
LACPTransmitRate=1

==> /etc/systemd/network/bond1.network <==
[Match]
Name=bond1

[Link]
MTUBytes=9000

[Network]
LinkLocalAddressing=no

[Network]
Address=10.230.0.4/22
Gateway=10.230.0.1

==> /etc/systemd/network/eth.network <==
[Match]
Name=eth*

[Network]
Bond=bond1